Methods and apparatus to validate an aircraft control system command

ABSTRACT

Methods, apparatus, and articles of manufacture to validate an aircraft control system command are disclosed. An example apparatus disclosed herein includes a detection module to determine a status of a component of a folding wingtip assembly operatively coupled to a wing of an aircraft and determine a flight stage of the aircraft. The example apparatus further includes a sequence and control module to generate a command to control a movement of the folding wingtip assembly, and a gatekeeper module to validate the command based on the status and the flight stage.

RELATED APPLICATIONS

This patent includes subject matter related to U.S. Pat. No. 9,290,260,which was filed on Sep. 10, 2013, U.S. Pat. No. 9,296,469, which wasfiled on Aug. 10, 2013, and U.S. Pat. No. 9,296,472, which was filed onOct. 17, 2013, all of which are hereby incorporated by reference intheir entireties.

FIELD OF THE DISCLOSURE

This disclosure relates generally to aircraft and, more particularly, tomethods and apparatus to validate an aircraft control system command.

BACKGROUND

In recent years, commercial aircraft manufacturers have beenincreasingly focused on designing and developing more fuel-efficientaircraft. An increase in fuel-efficiency produces cost savings over thelifetime of aircraft as fuel prices continue to trend higher. The fuelefficiency of an aircraft is typically a function of aerodynamic dragand fuel burn. The aerodynamic drag and the fuel burn of the aircraftmay be reduced as an aspect ratio of the aircraft wings is increased. Inaeronautics, a long, narrow wing has a high aspect ratio in comparisonto a short, wide wing, which has a low aspect ratio. Thus, increasing awingspan of an aircraft is an efficient method of increasing the aspectratio.

Increasing the wingspan of an aircraft may reduce the aerodynamic dragand the fuel burn of the aircraft. However, increasing the wingspan ofthe aircraft to lengths that are beyond the wingspans of currentaircraft may produce difficulties for conventional airports with limitedgate and taxiway spacing. Many airports can accommodate aircraft thathave a wingspan up to a conventional maximum length. By increasing thewingspan beyond the conventional maximum length, the aerodynamic dragand the fuel burn of the aircraft may be reduced at the expense of beingable to land and/or maneuver at airports.

SUMMARY

An example apparatus disclosed herein includes a detection module todetermine a status of a component of a folding wingtip assemblyoperatively coupled to a wing of an aircraft and determine a flightstage of the aircraft. The example apparatus further includes a sequenceand control module to generate a command to control a movement of thefolding wingtip assembly, and a gatekeeper module to validate thecommand based on the status and the flight stage.

An example method disclosed herein includes determining a status of acomponent of a folding wingtip assembly operatively coupled to a wing ofan aircraft, determining a flight stage of the aircraft, generating acommand to control a movement of the folding wingtip assembly, andvalidating the command based on the status and the flight stage.

An example tangible computer-readable storage medium includesinstructions, which when executed, cause a machine to at least determinea status of a component of a folding wingtip assembly operativelycoupled to a wing of an aircraft, determine a flight stage of theaircraft, generate a command to control a movement of the foldingwingtip assembly, and validate the command based on the status and theflight stage.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustration of an aircraft with a folding wingtipassembly coupled to both wings of the aircraft.

FIGS. 2A and 2B are block diagrams of an example implementation of anexample folding wingtip control module apparatus.

FIGS. 3-12 are flowcharts representative of example methods that may beused to implement the example folding wingtip control module apparatusof FIGS. 2A and 2B.

FIG. 13 is a block diagram of an example processing platform structuredto execute machine-readable instructions to implement the methods ofFIGS. 3-12 and the example folding wingtip control module apparatus ofFIGS. 2A and 2B.

The figures are not to scale. Instead, to clarify multiple layers andregions, the thickness of the layers may be enlarged in the drawings.Wherever possible, the same reference numbers will be used throughoutthe drawing(s) and accompanying written description to refer to the sameor like parts. As used herein, the terms “coupled” and “operativelycoupled” are defined as connected directly or indirectly (e.g., throughone or more intervening structures and/or layers).

DETAILED DESCRIPTION

In recent years, commercial aircraft manufacturers have invested inaircraft designs to improve profitability for commercial airlineoperators. Economics governing the modern air transportation industryhave influenced designs toward larger and/or more fuel-efficientaircraft. Larger aircraft can carry a greater number of passengers,thereby enabling an overall cost of each flight to be spread across thegreater number of passengers. Larger aircraft are also able to carryadditional fuel that may be used to deploy the aircraft on longer, moreexpensive flight routes.

Larger aircraft may burn additional fuel over a given travel distancedue to the increased weight of these aircraft. To counteract theincreased weight, one or more aircraft flight control surfaces (e.g., anelevator, a flap, a horizontal stabilizer, a rudder, a slat, a verticalstabilizer, a wing, etc.) may be added to the aircraft to reduce dragand/or enhance lift. In some examples, the one or more aircraft flightcontrol surfaces are controlled in flight to improve aerodynamicproperties of the aircraft. In some instances, the one or more aircraftflight control surfaces may be aerodynamically designed to reduce dragand enhance lift of the aircraft.

Aircraft wings, for example, may be designed to reduce drag bymanipulating an aspect ratio of the wings. In aeronautics, the aspectratio of the aircraft wings is the ratio of the span of the wings to themean chord of the wings. The span is the distance from one wingtip tothe other wingtip. The span is measured in a straight line from wingtipto wingtip, independently of wing shape or sweep. A chord is animaginary straight line joining a leading edge and a trailing edge ofthe aircraft wing. A chord length is a distance between the trailingedge and the point on the leading edge where the chord intersects theleading edge. Most aircraft wings are not rectangular so they have adifferent chord and corresponding chord length at different positionsalong the span of the aircraft wing. In some examples, the mean chord isa standard mean chord (SMC), where the SMC is defined as wing areadivided by wing span. In some instances, the mean chord is a meanaerodynamic chord (MAC), where the MAC is calculated using an integralsum of the chord lengths over the wingspan of the aircraft.

To increase the aspect ratio of aircraft wings, the wingspan may beincreased, the mean chord may be decreased, and/or a combinationthereof. Increasing the wingspan is an effective method of increasingthe aspect ratio of aircraft wings and reducing drag and/or enhancinglift of the aircraft. However, elongated wingspans may pose challengesto existing airport layouts. For example, an aircraft with an increasedor elongated wingspan may not fit in an allocated space at a gate of anairport terminal. Such aircraft wings may interfere with other aircraftand/or gates when attempting to dock at a designated gate of theaircraft terminal.

Example folding wingtip (FWT) apparatus disclosed herein are operativeto fold wingtips of an aircraft that has an elongated wingspan. Theexample FWT apparatus may be used to move the wingtips of an aircraftfrom an extended position (e.g., a flight position, an unfoldedposition, etc.) to a folded position. For example, the extended positionmay be a position where the wingtips of the aircraft are flush with acurvature of the wings of the aircraft. The folded position may be aposition where the wingtips of the aircraft are at an angle with respectto a horizontal axis of the wings of the aircraft. Alternatively, theexample FWT apparatus may be used to move the wingtips of the aircraftto an intermediate position between the extended position and the foldedposition. The example FWT apparatus may include actuators, motors, andsensors to extend and fold the wingtips of the aircraft. The actuatorsand the motors may be electrically, hydraulically, and/or pneumaticallyactuated. The sensors may monitor component information such as, forexample, a flow rate (e.g., a flow rate of hydraulic fluid), a pressure(e.g., an air pressure, a hydraulic pressure, etc.), a temperature(e.g., a temperature of hydraulic fluid), etc. The sensors may alsomonitor component status information such as, for example, a position ofa component (e.g., a position of a linear actuator, a position of alocking mechanism, etc.), a status of a motor (e.g., a speed of a motoris greater than zero revolutions per minute), etc.

Some disclosed example FWT apparatus disclosed herein are operative tofold wingtips of the aircraft based on a latch and lock system. Theexample FWT apparatus may include a plurality of latch pins that arelocked into a latch position by primary locks and secondary locks. Eachprimary lock mechanically blocks movement of a corresponding secondarylock to hold the secondary lock in a locked position when the primarylock is not in a locked position. The secondary locks are coupledtogether to cause the secondary locks to move together into and out fromlocked positions. A latch pin inhibitor blocks movement of the latch pininto the latch position. The latch pin inhibitor is moved to permitlatching after completing a folding or unfolding of the wingtip. Whenthe locks are in their locked positions, the secondary locksmechanically block the primary locks from moving out of their lockedpositions. The secondary locks are biased into their locked positionsvia actuators (e.g., electric actuators, hydraulic actuators, pneumaticactuators, etc.). In some disclosed examples, the FWT apparatus mayinclude one or more fold brakes to maintain the wingtips in a foldedposition.

In general, the example FWT apparatus disclosed herein utilizes anexample FWT control module to monitor and control the FWT apparatus. Theexample FWT control module may obtain sensor information and performcalculations based on the sensor information. In some examples, the FWTcontrol module determines a state and/or a status of a component of theexample FWT apparatus. For example, the FWT control module may obtain ameasurement from a position sensor and compare the measurement to aposition set point to determine if one or more components related to theposition sensor are non-operational (e.g., one or more components arenon-responsive) or operational (e.g., one or more components areresponsive, one or more components are functional, etc.). For example,the status of the component and/or the system may be operational,non-operational, responsive, non-responsive, etc. In some examples, theFWT control module may determine that an input (e.g., a measurement froma sensor, an input from a flight deck, etc.) includes a non-responsivestatus. For example, the input may include a null index value, a valuethat is out of a range of permitted values for the value, a value thatdoes not update when expected, etc.

The example FWT control module described herein may include additionalmodule apparatus to perform functions related to the monitoring and thecontrol of the example FWT apparatus. For example, the FWT controlmodule may include one or more sub-modules to perform the monitoring andcontrol functions of the FWT apparatus. The sub-modules may beresponsible for individual tasks such as, for example, obtaininginformation (e.g., network information, sensor information, etc.),determining a status of a sub-component or a sub-system of the exampleFWT apparatus, perform output command validations, etc. The sub-modulesmay be responsible for enabling different functions of the FWTapparatus, such as, for example, the FWT apparatus actuator system, aremote electronics unit, a component (e.g., an actuator, a motor, avalve, etc.), etc. In some examples, the enabling of the differentfunctions of the FWT apparatus includes modifying a value of a flag. Asused herein, the flag is a variable in computer and/or machine readableinstructions that may alert the FWT apparatus of a status of thefunction associated with the flag.

The example FWT control module described herein may determine and/orexecute one or more sequences to automatically (e.g., without userinput, without user control, etc.) control the FWT apparatus. In someexamples, the FWT control module may determine a normal operationsequence for the FWT apparatus based on the status of the sub-componentsand the sub-systems of the FWT apparatus. For example, the FWT controlmodule may determine a normal operation sequence to move the FWTapparatus from a folded position to the extended position. The normaloperation sequence may be based on the operational status of thesub-components and the sub-systems. In some examples, the FWT controlmodule may modify and/or prematurely end the normal operation sequencebased on the obtained status information.

In some instances, the FWT control module may determine and/or execute anon-responsive sequence to automatically (e.g., without user input,without user control, etc.) control the FWT apparatus based on thestatus of the sub-components and the sub-systems of the FWT apparatus.For example, the FWT control module may determine a non-responsivesequence to move the FWT apparatus from a folded position to asafe-state position. The non-responsive sequence may be based on thenon-responsive status of at least one of the sub-components and/or thesub-systems. In some examples, the FWT control module may prematurelyend the normal operation sequence and transition to the non-responsivesequence based on the obtained status information.

FIG. 1 is a schematic illustration of an aircraft 100. The aircraft 100includes wings 102,104 coupled to a fuselage 106. Engines 108,110 arecoupled to the wings 102,104. Slats 112,114 and flaps 116,118 areoperatively coupled to the wings 102,104. Additional aircraft controlsurfaces of the aircraft 100 include horizontal stabilizers 120,122operatively coupled to elevators 124,126 and a vertical stabilizer 128coupled to the fuselage 106.

In the illustrated example of FIG. 1, the wings 102,104 are depicted ashaving fixed surfaces 130,132 and moveable surfaces 134,136. The fixedsurfaces 130,132 may be inboard portions of the wings 102,104 that maybe attached to the fuselage 106, while moveable surfaces 134,136 may beoperable to move relative to the fixed surfaces 130,132. For example,the fixed surface 130 may be an inboard portion of the wing 102 whilethe moveable surface 134 may be operable to move relative to the fixedsurface 130. The moveable surfaces 134,136 may be operable relative toaxes 138,140. For example, the moveable surface 134 may be operablerelative to the axis 138.

In the illustrated example of FIG. 1, the moveable surfaces 134,136 maybe referred to as moveable, foldable, or folding wingtips of the wings102,104. For example, the moveable surface 134 may be a folding wingtipof the wing 102. As used herein, a folding wingtip is a wingtipconfigured to move relative to a fixed surface of the wing. The foldingwingtips may have different angles, movement patterns, sizes, and otherparameters, dependent on the aircraft arrangement and/or aircraftimplementation and/or application.

In the illustrated example of FIG. 1, the moveable surfaces 134,136 aredepicted in a folded position. The moveable surfaces 134,136 may movefrom extended positions 142,144 to the folded positions 146,148. Theextended positions 142,144 may be positions in which the moveablesurfaces 134,136 are at an angle of approximately zero degrees withrespect to the axes 138,140. For example, the moveable surface 134 maymove from the extended position 142 to the folded position 146 in adirection 150. In another example, the moveable surface 136 may movefrom the extended position 144 to the folded position 148 in a direction152. In some instances, the moveable surfaces 134,136 may move from theextended positions 142,144 to intermediate positions, where theintermediate positions are between the extended positions 142,144 andthe folded positions 146,148.

The aircraft 100 of FIG. 1 is an example of an aircraft in which afolding wingtip (FWT) apparatus 154,156 may be implemented. In theillustrated example, the FWT apparatus 154,156 may move the moveablesurfaces 134,136 from the extended positions 142,144 to the foldedpositions 146,148 or intermediate positions. In some examples, the FWTapparatus 154,156 may move the moveable surfaces 134,136 from the foldedpositions 146,148 to the extended positions 142,144 or intermediatepositions. Although there are two example FWT apparatus 154,156 depictedin the illustrated example, alternatively or additionally there may beone FWT apparatus or more than two FWT apparatus included in an aircraftimplementation where one or more than two folding wingtips are utilized.

In the illustrated example of FIG. 1, the FWT apparatus 154,156 of theaircraft 100 include example FWT control modules 158,160 to controland/or monitor the FWT apparatus 154,156. There are two example FWTcontrol modules 158,160 located near a cockpit 180 of the aircraft 100,however the FWT control modules 158,160 may have one or more partslocated elsewhere on the aircraft 100. Although there are two exampleFWT control modules 158,160 depicted in the illustrated example, theremay be one FWT control module or more than two FWT control moduleincluded in the aircraft implementation where one or more than twofolding wingtips are utilized.

In some examples, the aircraft 100 may have one or more FWT controlmodule for each aircraft control surface and/or FWT apparatus. Forexample, the aircraft 100 may use the FWT control modules 158,160 tomonitor and/or control the moveable surface 134 of the wing 102. Inanother example, the aircraft 100 may use the FWT control modules158,160 to monitor and/or control one or more of the slats 112,114, theflaps 116,118, the elevators 124,126, and/or the vertical stabilizer128. In some examples, the aircraft 100 may have a single FWT controlmodule to monitor and/or control a plurality of aircraft controlsurfaces and/or FWT apparatus. For example, the aircraft 100 may use theFWT control module 158 to monitor and/or control the moveable surfaces134,136 of the wings 102,104. In some examples, the FWT control modules158,160 monitor a plurality of aircraft control surfaces (e.g., anelevator, a flap, a folding wingtip, etc.) and cause an additionaldevice (e.g., an additional control module, an additional controlsystem, etc.) to control (e.g., send a command signal) the plurality ofaircraft control surfaces. For example, the FWT control modules 158,160may monitor a status of the elevator 124 and send the status to anelevator control module, where the elevator control module may use thestatus to control the elevator 124. In some instances, the FWT controlmodules 158,160 monitor the plurality of aircraft control surfacesindependently of the additional device (e.g., the additional controlmodule, the additional control system, etc.). For example, the FWTcontrol modules 158,160 may monitor the status of the elevator 124. Theelevator control module may monitor and/or control the elevator 124 withor without information (e.g., a command, an input, a status, etc.)received from the FWT control modules 158,160.

In the illustrated example of FIG. 1, the example FWT control modules158,160 may monitor statuses of the FWT apparatus 154,156, and based onthe statuses, control the FWT apparatus 154,156 to adjust position(s)thereof. For example, the FWT control modules 158,160 may obtain ameasurement from a sensor 162 to obtain flight phase information and/orflight stage information. In some examples, the FWT control modules158,160 may determine a flight phase or a flight stage from the obtainedflight phase information and/or the flight stage information. Forexample, the flight phase and/or the flight stage may correspond to theaircraft 100 in flight, in motion on a ground surface (e.g., taxiing toan aircraft gate), motionless on the ground surface (e.g., docked at anaircraft gate), landing, taking-off, etc. The example FWT controlmodules 158,160 may also obtain a measurement from sensors 164,166 todetermine the status of the component and/or the system of the FWTapparatus 154,156. For example, the sensors 164,166 may determine aposition of an actuator (e.g., an isolation valve, a pneumatic valve,etc.), a speed of a motor (e.g., a hydraulic motor, a servo motor,etc.), a pressure measurement (e.g., an air pressure, a hydraulicpressure, etc.), etc. There are example sensors 164,166 located on thewings 102,104 of the aircraft 100, however there may be additionalsensors located elsewhere on the aircraft 100 to monitor the componentsand/or the systems of the FWT apparatus 154,156. The example FWT controlmodules 158,160 may adjust the moveable surfaces 134,136 from deployedpositions to un-deployed positions. For example, the FWT control module158 may adjust the moveable surface 134 from the extended position 142to the folded position 146 based on at least one of the flight stageinformation, the component status, and/or the system status of the FWTapparatus 154, the measurement(s) from the sensor(s) 162,164,166 etc. Insome examples, the extended positions 142,144 are the deployedpositions. In some instances, the folded positions 146,148 are theundeployed positions.

In the illustrated example of FIG. 1, the example FWT control modules158,160 obtain information from and send commands to remote electronicsunits (REUs) 168,170. In the illustrated example, there is an REU oneach of the wings 102,104. For example, the REUs 168,170 are located onrespective ones of the wings 102,104. The REUs 168,170 may obtain sensorinformation from the sensors 164,166 related to the FWT apparatus154,156. The REUs 168,170 may also send commands (e.g., actuationcommands) to the components and/or the systems of the FWT apparatus154,156. For example, the REU 168 may send a command to an actuator ofthe FWT apparatus 154 to move the FWT apparatus 154 from the extendedposition 142 to the folded position 146. The REU 168 may obtain sensorinformation related to the FWT apparatus 154. For example, the REU 168may obtain a speed of a servo motor, a position of the moveable surface134, etc. from the FWT apparatus 154. Although there are two REUs168,170 depicted in FIG. 1, there may be one REU or more than two REUsto monitor and control the FWT apparatus 154,156. In some examples, theREUs 168,170 independently monitor and/or control the FWT apparatus154,156. For example, the REUs 168,170 may monitor and/or control theFWT apparatus 154,156 independently of receiving information (e.g., acommand, an input, a status, etc.) from the FWT control modules 158,160.For example, the REUs 168,170 may monitor and/or control the FWTapparatus 154,156 with or without receiving the information (e.g., thecommand, the input, the status, etc.) from the FWT control modules158,160, where the FWT control modules 158,160 are monitoring the FWTapparatus 154,156.

FIG. 2A is a block diagram of an example implementation of the foldingwingtip (FWT) control modules 158,160 of FIG. 1. The example FWT controlmodules 158,160 monitor and control the FWT apparatus 154,156 of FIG. 1.The example FWT control modules 158,160 include an example collectionmodule 200, an example detection module 210, an example enable systemmodule 230, an example monitor and annunciation module 240, an examplesequence and control module 250, an example database 270, and an examplegatekeeper module 280.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the collection module 200 to query, filter, obtain,process, and/or select an input 296 and/or information from the database270 regarding a value for a flag, a status, a state, a variable, etc.The input 296 may include one or more inputs. In some examples, thecollection module 200 obtains inputs from the REUs 168,170 that includemultiple data acquisition channels via a network 294. In the illustratedexample, the REU 168 has a data channel A 260 and a data channel B 261.The data channel A 260 is in communication with a component A 262 andthe data channel B 261 is in communication with a component B 263. TheREU 170 has a data channel C 264 and a data channel D 265. The datachannel C 264 is in communication with a component C 266 and the datachannel D is in communication with a component D 267. In some examples,the collection module 200 may disable or enable an input or data channelbased on the status of the component and/or the system in communicationwith the REUs 168,170. For example, the collection module 200 maydisable the data channel A 260 because the data channel A 260 isobtaining a non-responsive status from the component A 262. In anotherexample, the collection module 200 may enable the data channel B 261because the data channel B 261 is not obtaining a non-responsive statusfrom the component B 263. In yet another example, the collection module200 may disable the data channel A 260 and the data channel B 261. Thecollection module 200 may enable the data channel C 264 because the datachannel C 264 is not obtaining a non-responsive status from component C266. The collection module 200 may disable or enable additional datachannels in a similar manner as described above.

In some examples, the input 296 to the FWT control modules 158,160 viathe collection module 200 is obtained from an additional control module(e.g., an aircraft control surface control module, a flight controlmodule, etc.), an external computer system to an aircraft (e.g., acomputer system on another aircraft in the vicinity, a remote server, asatellite, etc.), an onboard sensor (e.g., an altitude sensor, a speedsensor, etc.), etc. The input 296 may be unprocessed information (e.g.,non-manipulated data from an additional control module, non-scaled datafrom a sensor, etc.) or processed information (e.g., manipulated datafrom an additional control module, scaled data from a sensor, etc.).

In some examples, the input 296 may be a calculated value based on theunprocessed information, the processed information, and/or a combinationthereof. In some instances, the input 296 may be obtained from thedatabase 270. For example, the collection module 200 may select aprevious value of a sensor measurement, a previous calculated value fora parameter, etc. to be used by one or more algorithms, processes,programs, etc. The collection module 200 outputs unprocessed informationand/or processed information based on the input 296 to the detectionmodule 210, the enable system module 230, the monitor and annunciationmodule 240, and the database 270.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the detection module 210 to determine a status of acomponent and/or a system of the FWT control modules 158,160. Forexample, the detection module 210 may determine the status of thecomponent and/or the system based on information provided by thecollection module 200. The information provided by the collection module200 may be unprocessed information (e.g., unscaled sensor information,calculated status information, etc.) and/or processed information (e.g.,scaled sensor information, calculated status information, etc.). In someexamples, the detection module 210 provides an input to an additionalmodule (e.g., the monitor and annunciation module 240) by modifying avalue of a variable (e.g., a flag) to be read by the additional moduleon a next control cycle of the FWT control modules 158,160. For example,the detection module 210 may set an alert flag and store the alert flagin the database 270 during a first control cycle. During a secondcontrol cycle, the monitor and annunciation module 240 may retrieve thealert flag from the database 270 and execute an action based on thealert flag. In the illustrated example, the detection module 210 outputsunprocessed information and/or processed information to the sequence andcontrol module 250 and the database 270.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the enable system module 230 to enable a function of acomponent, a system, etc. of the FWT apparatus 154,156 of FIG. 1. Forexample, the enable system module 230 may enable the function of thecomponent, the system, etc. based on information provided by thecollection module 200. The information provided by the collection module200 may be unprocessed information (e.g., unscaled sensor information,calculated status information, etc.) and/or processed information (e.g.,scaled sensor information, calculated status information, etc.). In someexamples, the enable system module 230 alerts the example FWT controlmodules 158,160 that the component, the system, etc. is enabled. In someinstances, the enable system module 230 enables the function of thecomponent, the system, etc. by modifying a value of a variable. Forexample, the enable system module 230 may enable the function of thecomponent, the system, etc. by modifying a value of a flag (e.g., a flagin computer and/or machine readable instructions). In some examples, theenable system module 230 provides an input to an additional module(e.g., the monitor and annunciation module 240) by modifying the valueof the variable (e.g., the flag) to be read by the additional module ona next control cycle of the FWT control modules 158,160. For example,the enable system module 230 may set an alert flag and store the alertflag in the database 270 during a first control cycle. During a secondcontrol cycle, the monitor and annunciation module 240 may retrieve thealert flag from the database 270 and execute an action based on thealert flag. In the illustrated example, the enable system module 230outputs unprocessed information and/or processed information to thesequence and control module 250 and the database 270.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the monitor and annunciation module 240 to performfunctions such as, for example, classify non-responsive statuses,generate alerts, monitor alerts, and send information to a userinterface associated with the FWT apparatus 154,156 of FIG. 1. In someexamples, the information is annunciated to an operator (e.g., amaintenance technician, a pilot, etc.) via the user interface and/or anadditional output device such as a light emitting diode (LED), aspeaker, etc. based on the alerts. In some examples, the monitor andannunciation module 240 monitors the status of a component and/or asystem for a change in the status. For example, the monitor andannunciation module 240 may monitor the status of the component. Thecomponent status may change from responsive status to non-responsivestatus. The monitor and annunciation module 240 may classify thenon-responsive status and generate an alert based on the componentstatus change. In some instances, the monitor and annunciation module240 may monitor a stage, an action, an event, etc. of an FWT apparatusoperation (e.g., folding a wingtip of an FWT apparatus, unfolding awingtip of an FWT apparatus, etc.). For example, the monitor andannunciation module 240 may monitor whether the FWT apparatus completesthe FWT apparatus operation, etc. The monitor and annunciation module240 may generate an alert based on whether the FWT apparatus completesthe stage, the action, the event, etc. of the FWT apparatus operation.

In some examples, the information provided by the monitor andannunciation module 240 may be unprocessed information (e.g., unscaledsensor information, calculated status information, etc.) and/orprocessed information (e.g., scaled sensor information, calculatedstatus information, etc.). For example, the monitor and annunciationmodule 240 may generate an alert regarding an identified non-responsivestatus of a component (e.g., a hydraulic solenoid, a pneumatic actuator,etc.) and send the alert to an FWT apparatus user interface. The monitorand annunciation module 240 outputs unprocessed information and/orprocessed information to the sequence and control module 250 and thedatabase 270.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the sequence and control module 250 to determine andexecute a sequence of events regarding an operation of the FWT apparatus154,156 of FIG. 1. In some examples, the sequence and control module 250automatically executes a normal operation sequence of events based onobtained information. For example, the sequence and control module 250may automatically determine and execute the normal operation sequence ofevents based on the information from the detection module 210 (e.g., theflight deck input information, the flight stage information, etc.), theenable system module 230 (e.g., the FWT apparatus enable information,the FWT apparatus actuator enable information, etc.), the monitor andannunciation module 240 (e.g., the alert information), and the database270. In some examples, the sequence and control module 250 determines astatus of a component and/or a system based on a sensor measurementprior to executing a stage or action of the normal operation sequence.For example, the sequence and control module 250 may determine thestatus of the component used in the first stage prior to the firststage, and so on for subsequent stages or actions of the normaloperation sequence. Additionally or alternatively, the sequence andcontrol module 250 may determine the status of the component used in thefirst stage during and/or after the first stage, and so on forsubsequent stages or actions of the normal operation sequence.

In some examples, the sequence and control module 250 determines that anFWT non-responsive sequence of events may be executed based on theinformation from the detection module 210 (e.g., the flight deck inputinformation, the flight stage information, etc.), the enable systemmodule 230 (e.g., the FWT apparatus enable information, the FWTapparatus actuator enable information, etc.), the monitor andannunciation module 240 (e.g., the alert information), and the database270. In some instances, the sequence and control module 250 determines astatus of a component and/or a system based on a sensor measurementprior to executing a stage or action of the non-responsive sequence. Forexample, the sequence and control module 250 may determine the status ofthe component used in the first stage prior to the first stage, and soon for subsequent stages or actions of the non-responsive sequence.Additionally or alternatively, the sequence and control module 250 maydetermine the status of the component used in the first stage duringand/or after the first stage, and so on for subsequent stages or actionsof the non-responsive sequence.

In some examples, the sequence and control module 250 may generatecommands and transmit the commands to corresponding components and/orsystems to execute the commands. For example, the sequence and controlmodule 250 may generate and transmit one or more outgoing electroniccommands to a component, a system, etc. of the FWT apparatus 154,156 ofFIG. 1. In some examples, the sequence and control module 250 maygenerate a plurality of commands and store them in a database for futureexecution. For example, the sequence and control module 250 may issue afirst command from a plurality of generated commands and store theremaining commands in the database 270. When the sequence and controlmodule 250 determines that the first command has been completed, thenthe sequence and control module 250 may retrieve the second command fromthe database 270 and issue the second command, and so on for additionalgenerated commands.

In some examples, the sequence and control module 250 provides an inputto an additional module (e.g., the monitor and annunciation module 240)by modifying a value of a variable (e.g., a flag) to be read by theadditional module on a next control cycle of the FWT control modules158,160. For example, the sequence and control module 250 may set analert flag and store the alert flag in the database 270 during a firstcontrol cycle. During a second control cycle, the monitor andannunciation module 240 may retrieve the alert flag from the database270 and execute an action based on the alert flag.

In the illustrated example of FIG. 2A, the FWT control modules 158,160include the database 270 to record data (e.g., obtained sensorinformation, obtained component statuses, calculated parameter valuesetc.). The database 270 may be implemented by a volatile memory (e.g., aSynchronous Dynamic Random Access Memory (SDRAM), Dynamic Random AccessMemory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM), etc.) and/ora non-volatile memory (e.g., flash memory). The database 270 mayadditionally or alternatively be implemented by one or more double datarate (DDR) memories, such as DDR, DDR2, DDR3, mobile DDR (mDDR), etc.The database 270 may additionally or alternatively be implemented by oneor more mass storage devices such as hard disk drive(s), compact diskdrive(s) digital versatile disk drive(s), etc. While in the example thedatabase 270 is illustrated as a single database, the database 270 maybe implemented by any number and/or type(s) of databases.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 include the gatekeeper module 280 to monitor and/or interceptoutgoing electronic commands to a component and/or a system of the FWTapparatus 154,156 of FIG. 1. For example, the gatekeeper module 280intercepts the outgoing electronic commands from the sequence andcontrol module 250. In some examples, the gatekeeper module 280 obtainsinformation related to the flight stage information, the FWT statusinformation, etc. and enables the outgoing electronic commands toproceed unobstructed. In some instances, the gatekeeper module 280modifies the outgoing electronic commands based on the obtainedinformation. The gatekeeper module 280 produces output 298, where theoutputs 298 are unmodified or modified outgoing electronic commands. Theoutput 298 may include one or more outputs. The gatekeeper module 280also may output unprocessed and/or processed information to the database270. For example, the gatekeeper module 280 may store a value of theunmodified or the modified outgoing electronic command in the database270.

In some examples, the gatekeeper module 280 may be used to monitorand/or intercept outgoing electronic commands to an aircraft controlsurface. For example, the gatekeeper module 280 may monitor a command toactuate or control one or more of the slats 112,114, the flaps 116,118,the elevators 124,126, and/or the vertical stabilizer 128 of FIG. 1. Thegatekeeper module 280 may verify that the command controlling theaircraft control surface is valid. For example, the gatekeeper module280 may verify that the command is valid based on the flight deck inputinformation, the flight stage information, or, more generally, theinformation related to the aircraft control surface of the aircraft 100of FIG. 1.

In the illustrated example of FIG. 2A, the example FWT control modules158,160 may be connected to the REUs 168,170 of FIG. 1 via a network294. The input 296 and the output 298 may be in communication with thenetwork 294. The network 294 of the illustrated example of FIG. 1 is anaircraft process control network. However, the example network 294 maybe implemented using any suitable wired and/or wireless network(s)including, for example, one or more data buses, one or more aircraftprocess control networks, one or more Local Area Networks (LANs), one ormore wireless LANs, one or more cellular networks, one or more privatenetworks, one or more public networks, etc. The network 294 enables theexample FWT control modules 158,160 to be in communication with the REUs168,170. As used herein, the phrase “in communication,” includingvariances therefore, encompasses direct communication and/or indirectcommunication through one or more intermediary components and does notrequire direct physical (e.g., wired) communication and/or constantcommunication, but rather includes selective communication at periodicor aperiodic intervals, as well as one-time events.

FIG. 2B is a block diagram of the example implementation of the foldingwingtip (FWT) control modules 158,160 as described in FIG. 2A. The blockdiagram of FIG. 2A details example sub-modules or example sub-systemsthat may perform the monitoring and control functions of the FWTapparatus 154,156 of FIG. 1. The example sub-modules follow the dataflow paths and information delivery dependencies described in FIG. 2A.

The collection module 200 of FIGS. 2A and 2B includes an example networkinterface 202, an example sensor interface 204, an example informationprocessor 206, and an example information validator 208. The collectionmodule 200 includes the network interface 202 to provide an interface toa bus and/or a network. For example, the network interface 202 may be aninternal controller bus, an internal process control network, etc. Thenetwork interface 202 may implement one or more communication protocolssuch as, for example, bus protocols (controller area network (CAN) bus,Modbus, Profibus, etc.), Ethernet protocols (e.g., EtherCAT, Profinet,etc.), serial protocols (e.g., RS-232, RS-485, etc.) The networkinterface 202 may be implemented using any suitable wired and/orwireless network interface(s) including, for example, one or more databuses, one or more Local Area Networks (LANs), one or more wirelessLANs, one or more cellular networks, one or more fiber optic networks,one or more satellite networks, one or more private networks, one ormore public networks, etc.

In some examples, the network interface 202 enables the example FWTcontrol modules 158,160 to be in communication with external modulesand/or external systems to the FWT control modules 158,160. For example,the network interface 202 may enable the FWT control modules 158,160 tobe in communication with the REUs 168,170 of FIG. 1. In some examples,the network interface 202 obtains information from the REUs 168,170. Forexample, the network interface 202 may obtain a component status, asensor measurement, a system status, etc. from the REUs 168,170. In someexamples, the network interface 202 stores the obtained information fromthe REUs 168,170 in the database 270.

The collection module 200 of FIGS. 2A and 2B includes the sensorinterface 204 to interface with sensors and/or additional dataacquisition systems that interface with sensors. For example, the sensorinterface 204 may enable the FWT control modules 158,160 to be incommunication with the sensor 162. The sensor interface 204 is aninterface that collects and/or obtains sensor information. The sensorinformation may be obtained from sensors that output analog electricalsignals (e.g., current measurements, voltage measurements, etc.) suchas, for example, accelerometers, light sensors, pressure sensors, soundsensors, temperature sensors, etc. The sensor information may beobtained from sensors that output digital electrical signals such as,for example, digital accelerometers, digital temperature sensors, etc.Additional sensors with analog outputs and/or digital outputs mayinclude, for example, chemical sensors, flow sensors, force sensors,heat sensors, magnetic sensors, position sensors, presence sensors,proximity sensors, speed sensors, etc.

The collection module 200 of FIGS. 2A and 2B includes the informationprocessor 206 to select and/or process an input to the FWT controlmodules 158,160. For example, the information processor 206 may selectand/or process the input 296. In some examples, the informationprocessor 206 selects obtained inputs of interest to be used by one ormore algorithms, processes, programs, etc. For example, the informationprocessor 206 may process a value of an input by converting (e.g.,converting using a conversion calculation, converting to different unitsof measure, etc.), scaling (e.g., scaling using a scaling factor),and/or translating (e.g., translating using a pre-determined curve,translating using a pre-determined equation) the value of the input 296for use by the FWT control modules 158,160. In some examples, theinformation processor 206 selects the input 296 by querying the database270. In response to the database 270 receiving the query sent from theinformation processor 206, the database 270 transmits the input 296 tothe information processor 206.

The collection module 200 of FIGS. 2A and 2B includes the informationvalidator 208 to validate an input to the FWT control modules 158,160.For example, the information validator 208 may validate the input 296.In some examples, the information validator 208 analyzes the input 296to determine whether the input 296 is to be deemed reliable and/ortrustworthy and subsequently to be used by the FWT control modules158,160. In some examples, the information validator 208 compares theinput 296 to a range of acceptable values for the input 296. Theinformation validator 208 may obtain the range of acceptable values forthe input 296 from the database 270. In response to obtaining the rangeof acceptable values, the information validator 208 may compare theinput 296 to the obtained range of acceptable values. For example, theinformation validator 208 may analyze a pressure measurement input of1000 pounds per square inch (PSI) for a pressure sensor. The informationvalidator 208 may obtain a pressure range of 0-600 PSI for the pressuresensor from the database 270. In response to obtaining the pressurerange for the pressure sensor, the information validator 208 may comparethe pressure measurement input of 1000 PSI to the obtained pressurerange of 0-600 PSI and determine that the pressure measurement input isout of range. In response to determining that the input 296 is out ofrange, the information validator 208 may invalidate the input 296 byignoring the input 296, setting the value of the input 296 to anothervalue (e.g., to a known valid value, to a zero value, to a null value,etc.). The information validator 208 may also alert the FWT controlmodules 158,160 that the input 296 is invalid. For example, theinformation validator 208 may set a flag (e.g., an invalid input flag,an alert flag, etc.) alerting the FWT control modules 158,160 that theinput 296 is invalid.

In some examples, the information validator 208 analyzes the input 296to determine whether the input 296 is valid based on a status of anaircraft (e.g., an aircraft is above 10,000 feet, landing gear has beendeployed, etc.). For example, the information validator 208 maydetermine that although though the value of the input 296 is within anacceptable range of values for the input 296, the value of the input 296is invalid based on the status of the aircraft. For example, theinformation validator 208 may receive the input 296, where the input 296is a command input to enable the FWT actuation system to move themoveable surface 134 of FIG. 1 from the extended position 142 to thefolded position 146. The information validator 208 may determine thatthe value of the command input is within an acceptable range of valuesfor the command input. However, the information validator 208 maydetermine that the aircraft is in flight (e.g., the aircraft has a speedabove 100 miles per hour, the aircraft is at an altitude greater than1,000 feet, etc.). In response to determining that the aircraft is inflight, the information validator 208 invalidates the command input. Forexample, the information validator 208 may set the value of the input296 to zero and set a flag (e.g., an invalid input flag) alerting theFWT control modules 158,160 that the value of the input 296 is invalid.

The detection module 210 of FIGS. 2A and 2B includes an example flightdeck input detector 212, an example flight stage detector 214, anexample FWT status detector 216, an example FWT detent detector 218, andan example FWT lock detector 220. The detection module 210 of FIGS. 2Aand 2B includes the flight deck input detector 212 to detect a status ofan input from a cockpit or flight deck of an aircraft. For example, theflight deck input detector 212 may obtain the flight deck input statusinformation from the flight deck of the aircraft 100. The flight deck isan area typically near the front of the aircraft from which a pilotcontrols the aircraft. The flight deck of the aircraft includes flightinstruments on an instrument panel, flight controls that enable thepilot to fly the aircraft, etc.

In some examples, the flight deck includes the flight instruments and/orthe flight controls for an FWT apparatus. For example, the flight deckmay include buttons, knobs, levers, switches, etc. that the pilot mayactuate to provide an input to the FWT control modules 158,160 tomonitor and/or to control the FWT apparatus 154,156 of FIG. 1. In someexamples, actuating one or more of the buttons, knobs, levers, switches,etc. in the flight deck begins a folding wingtip operation (e.g.,folding moveable surfaces 134,136, unfolding moveable surfaces 134,136,etc.). For example, the flight deck may include a lever, that whenactuated, provides the input 296 to the FWT control modules 158,160 tomove the FWT apparatus 154,156 to the extended positions 142,144. Theflight deck input detector 212 may determine that the status of thelever (e.g., the output of the lever) is either enabled (e.g., move theFWT apparatus 154,156 to the extended positions 142,144) or disabled(e.g., do not move the FWT apparatus 154,156 to the extended positions142,144). For example, when the lever is actuated to move the FWTapparatus 154,156 from the folded positions 146,148 to the extendedpositions 142,144, the flight deck input detector 212 may determine thatthe input 296 from the lever is enabled.

The detection module 210 of FIGS. 2A and 2B includes the flight stagedetector 214 to detect a stage of a flight plan or a flight stage beingexecuted by an aircraft during a time period. A flight plan may includeflight stages such as, for example, disembarking from an airport gate,taxiing to a runway, taking off from the runway, flying at a cruisingaltitude, landing on the runway, etc. In some examples, the flight stagedetector 214 determines the flight stage of the aircraft based on ameasurement of a sensor (e.g., a measurement from an altitude sensor, ameasurement from a speed sensor, a measurement from a landing gearposition sensor, etc.). In some instances, the flight stage detector 214determines the flight stage of the aircraft based on a status of theaircraft such as, for example, a deployment of landing gear, adecreasing altitude of the aircraft, etc.

The detection module 210 of FIGS. 2A and 2B includes the FWT statusdetector 216 to detect a status of an FWT apparatus. For example, theFWT status detector 216 may detect the statuses of the FWT apparatus154,156 of FIG. 1. In some examples, the status of the FWT apparatus maybe a mode of the FWT apparatus. The mode may be, for example, an activemode (e.g., a mode that involves folding a wingtip, a mode that involvesunfolding a wingtip, etc.) or a standby mode (e.g., a mode that involvesa wingtip not moving). For example, the FWT status detector 216 maydetect the status of the FWT apparatus 154,156 to be in the active modeor in the standby mode. In some examples, the status of the FWTapparatus may be a position of the FWT apparatus. For example, thestatuses of the FWT apparatus 154,156 may be the positions of themoveable surfaces 134,136 of FIG. 1, where the positions are theextended positions 142,144, the folded positions 146,148, or theintermediate positions. For example, the FWT status detector 216 maydetect the status of the FWT apparatus 154 to be the extended position,the folded position, the intermediate position, etc.

The detection module 210 of FIGS. 2A and 2B includes the FWT detentdetector 218 to detect a position of one or more latch pins of an FWTapparatus. For example, the FWT detent detector 218 may detect theposition of one or more latch pins of the FWT apparatus 154,156 ofFIG. 1. In some examples, the FWT detent detector 218 determines theposition to be a latched position (e.g., an extended position) or anunlatched position (e.g., a retracted position). The latch pins may belatched or extended when the wingtips are in the folded position or theextended position. For example, the FWT detent detector 218 maydetermine that the latch pins are extended based on a measurement from alatch position sensor (e.g., an inductive proximity sensor, an angleposition sensor, a linear position sensor, etc.). The latch pins may beretracted when the FWT apparatus 154,156 are in the process of movingfrom one position to another position. For example, the FWT detentdetector 218 may determine that the latch pins of the FWT apparatus154,156 are retracted based on the measurement from the latch positionsensor.

The detection module 210 of FIGS. 2A and 2B includes the FWT lockdetector 220 to detect a position of one or more locks of an FWTapparatus. For example, the FWT lock detector 220 may detect theposition of one or more locks of the FWT apparatus 154,156 of FIG. 1. Insome examples, the FWT lock detector 220 determines the position to be alocked position, an unlocked position, or an intermediate position(e.g., a middle position, a position between the locked position and theunlocked position, etc.). The FWT lock detector 220 may detect theposition for a plurality of locks such as, for example, one or moreprimary locks, one or more secondary locks, etc. For example, the FWTlock detector 220 may determine that the position of a primary lock ofthe FWT apparatus 154,156 are in the locked position. In anotherexample, the FWT lock detector 220 may determine that the position of asecondary lock is in the middle position. In some examples, the FWT lockdetector 220 determines the position of the primary locks and/or thesecondary locks based on a measurement from a lock position sensor(e.g., an inductive proximity sensor, an angle position sensor, a linearposition sensor, etc.).

The enable system module 230 of FIGS. 2A and 2B includes an example FWTapparatus enabler 232, an example FWT apparatus actuator system enabler234, an example REU enabler 236, and an example component enabler 238.The enable system module 230 of FIGS. 2A and 2B includes the FWTapparatus enabler 232 to enable an FWT apparatus. For example, the FWTapparatus enabler 232 may enable the FWT apparatus 154,156 of FIG. 1. Insome examples, the FWT apparatus enabler 232 may set a flag (e.g., anenable flag, an alert flag, etc.) alerting the FWT control modules158,160 that the FWT apparatus is enabled and/or disabled. For example,the FWT apparatus enabler 232 may set an enable FWT apparatus flag toenable the monitoring and/or the controlling of the FWT apparatus154,156 by the FWT control modules 158,160.

In some examples, in response to the FWT apparatus enabler 232 enablingthe FWT apparatus 154,156, the FWT control modules 158,160 are permittedto perform a plurality of actions. For example, in response to the FWTapparatus enabler 232 enabling the FWT apparatus 154,156 (e.g., bysetting the enable FWT apparatus flag for the FWT apparatus 154,156),the FWT control modules 158,160 may perform a function such as actuatinga component of the FWT apparatus 154,156 (e.g., locking a primary lock,extending a latch pin, etc.), enabling a sub-system of the FWT apparatus154,156 (e.g., enabling the FWT apparatus actuator, enabling the remoteelectronics unit, etc.), etc. In some instances, the FWT control modules158,160 cannot monitor and/or control the FWT apparatus without the FWTapparatus enabler 232 enabling the FWT apparatus. For example, if theFWT apparatus enabler 232 does not set the enable FWT apparatus flag forthe FWT apparatus 154,156 then the FWT control modules 158,160 may notbe permitted to monitor and/or to control the FWT apparatus 154,156.

The enable system module 230 of FIGS. 2A and 2B further includes the FWTapparatus actuator system enabler 234 to enable an actuator system of anFWT apparatus. For example, the FWT apparatus actuator system enabler234 may enable the actuator system (e.g., the hydraulic system, thepneumatic system, etc.) of the FWT apparatus 154,156 of FIG. 1. In someexamples, the FWT apparatus actuator system enabler 234 may set a flag(e.g., an enable flag, an alert flag, etc.) alerting the FWT controlmodules 158,160 that the FWT apparatus actuator system is enabled and/ordisabled. For example, the FWT apparatus actuator system enabler 234 mayset an enable FWT apparatus actuator system flag to enable themonitoring and/or the controlling of the FWT apparatus actuator systemof the FWT apparatus 154,156 by the FWT control modules 158,160.

In some examples, in response to the FWT apparatus actuator systemenabler 234 enabling the FWT apparatus actuator system, the FWT controlmodules 158,160 are permitted to perform a plurality of actions. Forexample, in response to the FWT apparatus actuator system enabler 234enabling the FWT apparatus actuator system of the FWT apparatus 154,156(e.g., by setting the enable FWT apparatus actuator system flag), theFWT control modules 158,160 may perform a function such as actuating acomponent of the FWT actuator system (e.g., actuating a solenoid,actuating a servo motor, actuating a valve, etc.), enabling a sub-systemof the FWT apparatus actuator system (e.g., enabling an electricalsystem, enabling a hydraulic system, enabling a pneumatic system, etc.),etc. In some instances, the FWT control modules 158,160 cannot monitorand/or control the FWT apparatus actuator system without the FWTapparatus actuator system enabler 234 enabling the FWT apparatusactuator system. For example, if the FWT apparatus actuator systemenabler 234 does not set the enable FWT apparatus actuator system flagfor the FWT apparatus 154,156, then the FWT control modules 158,160 maynot be permitted to monitor and/or to control the FWT apparatus actuatorsystem of the FWT apparatus 154,156.

The enable system module 230 of FIGS. 2A and 2B additionally includesthe remote electronics unit (REU) enabler 236 to enable an REU. Forexample, the REU enabler 236 may enable the REUs 168,170 of FIG. 1. Insome examples, the REU enabler 236 may set a flag (e.g., an enable flag,an alert flag, etc.) alerting the FWT control modules 158,160 that theREUs 168,170 is enabled and/or disabled. For example, the REU enabler236 may set an enable REU flag to enable the monitoring and/or thecontrolling of the REUs 168,170 by the FWT control modules 158,160. Insome examples, the enabling of the REU enables the REU to perform afunction such as, for example, actuating a component of the FWT actuatorsystem (e.g., actuating a solenoid, actuating a servo motor, etc.)enabling a sub-system of the FWT actuator system (e.g., enabling anelectrical system, enabling a hydraulic system, enabling a pneumaticsystem, etc.), obtain sensor information, etc.

In some examples, in response to the REU enabler 236 enabling the REUs168,170, the FWT control modules 158,160 are permitted to perform aplurality of actions. For example, in response to the REU enabler 236enabling the REUs 168,170 (e.g., by setting the enable REU flag for theREUs 168,170), the FWT control modules 158,160 may perform a functionsuch as actuating a component of the FWT apparatus 154,156 (e.g.,locking a primary lock, extending a latch pin, etc.) via the REUs168,170. In some instances, the FWT control modules 158,160 cannotmonitor and/or control the REUs 168,170 without the REU enabler 236enabling the REUs 168,170. For example, if the REU enabler 236 does notset the enable REU flag for the REUs 168,170, then the FWT controlmodules 158,160 may not be permitted to monitor and/or to control theREUs 168,170.

The enable system module 230 of FIGS. 2A and 2B further includes thecomponent enabler 238 to enable one or more components of an FWTapparatus. For example, the component enabler 238 may enable one or morecomponents of the FWT apparatus 154,156 of FIG. 1. A component of theFWT apparatus 154,156 may include, for example, an actuator, a motor, asolenoid, a valve, etc. The component may also include FWT apparatuscomponents such as, for example, a fold brake, a latch pin, a lock(e.g., a primary lock, a secondary lock, etc.), etc. For example, thecomponent may be a primary lock of the FWT apparatus 154,156. Thecomponent of the FWT apparatus may include a sensor that obtains ameasurement and/or a status of the component. In some examples, thecomponent enabler 238 may enable the component based on the sensormeasurement. For example, the component enabler 238 may enable ahydraulic motor based on a measurement from a hydraulic pressure sensorthat satisfies a threshold (e.g., a measurement from a hydraulicpressure that is greater than 500 PSI). In some examples, the componentenabler 238 may set a flag (e.g., an enable flag, an alert flag, etc.)alerting the FWT control modules 158,160 that the one or more componentsare enabled. For example, the component enabler 238 may set an enablecomponent flag to enable the monitoring and/or the controlling of thecomponent by the FWT control modules 158,160.

In some examples, in response to the component enabler 238 enabling thecomponent, the FWT control modules 158,160 are permitted to perform aplurality of actions. For example, in response to the component enabler238 enabling the component, the FWT control modules 158,160 may performan action such as actuating the component of the FWT apparatus 154,156(e.g., opening a valve, locking a primary lock, extending a latch pin,etc.). In another example, in response to the component enabler 238enabling the component, the FWT control modules 158,160 may obtaininformation from a sensor monitoring the component. For example, inresponse to the component enabler 238 enabling the component, the FWTcontrol modules 158,160 may obtain information from a speed sensormonitoring a speed of a hydraulic motor of the FWT apparatus 154,156. Insome instances, the FWT control modules 158,160 cannot monitor and/orcontrol the component without the component enabler 238 enabling thecomponent. For example, if the component enabler 238 does not set theenable component flag for a servo motor, then the FWT control modules158,160 may not be permitted to monitor and/or to control the servomotor.

The monitor and annunciation module 240 of FIGS. 2A and 2B includes anexample non-responsive status classifier 242, an example alert generator244, an example alert manager 246, and an example user interfaceinformation provider 248. The monitor and annunciation module 240includes the non-responsive status classifier 242 to classify anon-responsive status of a component. For example, the non-responsivestatus classifier 242 may classify a non-responsive status of apneumatic actuator for the FWT apparatus 154,156 of FIG. 1. In someexamples, the non-responsive status classifier 242 obtains one or morenon-responsive statuses from the database 270. In some instances, thenon-responsive status classifier 242 selects a non-responsive status toclassify and/or to process from a plurality of obtained non-responsivestatuses.

In some examples, the non-responsive status classifier 242 classifiesthe non-responsive status as an isolated or a systemic issue. Forexample, the non-responsive status classifier 242 may obtain anon-responsive status of a first component (e.g., a pneumatic actuator).The non-responsive status classifier 242 may subsequently obtain astatus for a second component (e.g., an air pressure sensor, where thesecond component is related to the first component (e.g., the airpressure sensor is monitoring the pneumatic actuator). If the secondcomponent also returns a non-responsive status, then the non-responsivestatus classifier 242 may classify the non-responsive status of thefirst component as a systemic issue because both the first component andthe second component have a non-responsive status. For example, thepneumatic actuator may be non-responsive because the air pressuremeasured by the air pressure sensor is below a sufficient levelnecessary to actuate the pneumatic actuator. If the second componentdoes not return a non-responsive status, then the non-responsive statusclassifier 242 may classify the non-responsive status of the firstcomponent as an isolated issue to the first component. For example, themeasured air pressure may be at a sufficient level to actuate thepneumatic actuator. The pneumatic actuator may be non-responsive becauseof another issue (e.g., a pneumatic valve is not open to provide air tothe pneumatic actuator).

In some examples, the non-responsive status classifier 242 determineswhether a non-responsive status of a component and/or a system can bemitigated. For example, the non-responsive status classifier 242 maydetermine that a component of the FWT apparatus 154,156 may be bypassedin response to the component having a non-responsive status. In someexamples, the non-responsive status classifier 242 determines that thecomponent with the non-responsive status has one or more redundantcomponents. For example, the non-responsive status classifier 242 maydetermine that a hydraulic pressure sensor monitoring a hydraulic valvehas a non-responsive status. The non-responsive status classifier 242may determine that there is at least one additional hydraulic pressuresensor monitoring the hydraulic valve that does not have anon-responsive status. In response to determining that there is aredundant component, the non-responsive status classifier 242 may alertthe FWT control modules 158,160 that the non-responsive status of thecomponent can be mitigated. For example, the non-responsive statusclassifier 242 may set a flag (e.g., a bypass flag, a redundantcomponent flag, a mitigation flag, etc.) alerting the FWT controlmodules 158,160 that the component with the non-responsive status may bebypassed.

The monitor and annunciation module 240 of FIGS. 2A and 2B includes thealert generator 244 to generate an alert based on the informationobtained from the collection module 200 and/or the database 270. In someexamples, the alert generator 244 may evaluate the information anddetermine if the information satisfies a threshold. The threshold may bea calculated value, a pre-determined value, etc. For example, the alertgenerator 244 may determine that a measurement from a hydraulic pressuresensor does not satisfy a hydraulic pressure threshold (e.g., ameasurement is below a hydraulic pressure threshold). The measurementnot satisfying the hydraulic pressure threshold may indicate that ahydraulic actuator monitored by the hydraulic pressure sensor is notresponsive, that a hydraulic motor monitored by the hydraulic pressuresensor is non-responsive, etc.

In some examples, the alert generator 244 determines that a status froma component and/or a system requires a generation of an alert. Forexample, the alert generator 244 may determine that an obtained statusfrom an electrically actuated solenoid is a non-responsive status andthus requires a generation of an alert. The alert generator 244 mayobtain the electrically actuated solenoid status from the collectionmodule 200 and/or the database 270. In some examples, the alertgenerator 244 assigns an index and/or a priority to the generated alert.For example, the index may be a criticality index that indicates a levelof importance for a component and/or a system referred to in thegenerated alert. In response to identifying a status necessitating ageneration of an alert (e.g., a measurement satisfying a threshold, achange in a component and/or a system status, etc.), the alert generator244 may generate an alert such as, for example, displaying an alert on auser interface, propagating an alert message throughout a processcontrol network, generating an alert log and/or an alert report, etc.

The monitor and annunciation module 240 of FIGS. 2A and 2B includes thealert manager 246 to manage the alerts generated by the alert generator244. In some examples, the alert manager 246 processes the generatedalerts by compiling them in a list, a log, a report, etc. For example,the alert manager 246 may collect the plurality of generated alerts andorganize them in an alert report. The alert report may includeinformation regarding individual alerts such as, for example, atimestamp, an index, a priority, a text-based description, an alertcategory, etc. In some instances, the alert report includes informationregarding trend analysis of recurring alerts. For example, the alertreport may indicate that a non-responsive pneumatic actuator alertoccurs whenever the FWT apparatus 154,156 are actuated or when anaircraft achieves an altitude greater than 10,000 feet. In someexamples, the alert manager 246 may be accessible from a user interface.For example, the alert manager 246 may be a sub-display, a sub-module,etc. of a human machine interface (HMI) in the cockpit. A pilot in thecockpit may interact with the alert manager 246 via the HMI, where thepilot may acknowledge an alert, dismiss an alert, conduct an actionbased on an alert, review an alert report, review an alert trendanalysis, etc.

The monitor and annunciation module 240 of FIGS. 2A and 2B includes theuser interface information provider 248 to process, package, and provideinformation to a user interface associated with an FWT apparatus. Forexample, the user interface information provider 248 may obtain andtransmit information to a user interface associated with the FWTapparatus 154,156 of FIG. 1. The information may include a stage and/oran action related to an FWT apparatus operation, a status of a componentand/or a system related to the FWT apparatus, an alert generated by themonitor and annunciation module, etc. In some examples, the userinterface information provider 248 assigns a value associated with acomponent status and/or a system status to a variable associated withthe user interface. In some instances, the user interface informationprovider 248 assigns information related to a generated alert to avariable associated with the user interface. In some examples, thevariables may be displayed and/or logged on the user interface. Forexample, the user interface information provider 248 may assign ameasurement obtained from a hydraulic pressure sensor to a variableassociated with the user interface. The variable may be transmitted tothe user interface via the network 294. The variable may be stored inthe database 270 and obtained by the user interface from the database270.

The sequence and control module 250 of FIGS. 2A and 2B includes anexample FWT normal operation sequencer 252, an example FWTnon-responsive sequencer 254, an example status evaluator 256, and anexample FWT controller 258. The sequence and control module 250 includesthe FWT normal operation sequencer 252 to determine a normal operationsequence of FWT stages and/or FWT actions to move a position of themoveable surfaces 134,136. In some examples, the FWT normal operationsequencer 252 determines the normal operation sequence based on a sensormeasurement, a component status, a system status, etc. For example, theFWT normal operation sequencer 252 may determine the normal operationsequence based on a sensor measurement that satisfies a threshold (e.g.,a sufficient threshold, a satisfactory threshold, a necessary threshold,etc.). In another example, the FWT normal operation sequencer 252 maydetermine the normal operation sequence based on the component statusand/or the system status, where the statuses do not indicate anon-responsive status.

In some examples, the FWT normal operation sequencer 252 identifies oneor more FWT stages to execute a movement of the moveable surfaces134,136 based on the obtained information (e.g., the flight deck inputinformation, the flight stage information, etc.). In some examples, theFWT normal operation sequencer 252 identifies the FWT stages prior toexecuting the first FWT stage. For example, the FWT normal operationsequencer 252 may determine that there are three FWT stages to beexecuted to move the moveable surfaces 134,136 from the extendedpositions 142,144 to the folded positions 146,148. In some instances,the FWT normal operation sequencer 252 determines the FWT actions thatwill be executed within each of the determined FWT stages prior toexecuting the first FWT stage. For example, the FWT normal operationsequencer 252 may determine that there are three FWT stages and four FWTactions within each of the three FWT stages to be executed to move themoveable surfaces 134,136 from the extended positions 142,144 to thefolded positions 146,148. In some examples, the FWT normal operationsequencer 252 calculates and/or identifies a desired position of the FWTapparatus based on the obtained information. For example, the FWT normaloperation sequencer 252 may calculate a desired position of the moveablesurface 134 of the FWT apparatus 154 based on the obtained flight stageinformation of the aircraft 100. The FWT normal operation sequencer 252may generate one or more stages and/or actions to cause the moveablesurface 134 of the FWT apparatus 154 to move to the desired positionfrom the current position of the moveable surface 134.

In some examples, the FWT normal operation sequencer 252 obtains andevaluates information prior to an execution of an FWT stage or an FWTaction within the FWT stage. The FWT normal operation sequencer 252 mayidentify a first FWT action within a first FWT stage. For example, theFWT normal operation sequencer 252 may identify a first FWT action(e.g., opening an isolation valve) within a first FWT stage of adjustingthe position of the moveable surfaces 134,136 of FIG. 1 from theextended positions 142,144 to the folded positions 146,148. For example,the FWT normal operation sequencer 252 may obtain information related tothe first FWT action such as, for example, flight stage information, FWTstatus information, etc. to determine if the moveable surfaces 134,136may be moved based on the obtained information. Additionally oralternatively, the FWT normal operation sequencer 252 may obtain andevaluate information during and/or after the execution of the FWT stageor the FWT action within the FWT stage.

In some examples, the FWT normal operation sequencer 252 obtainsinformation related to the components and/or the systems involved in thefirst FWT action prior to the first FWT action. For example, if thefirst FWT action is to unlock a primary lock of the FWT apparatus154,156 using a hydraulic actuator, then the FWT normal operationsequencer 252 may obtain an enable hydraulic actuator status, ameasurement from a hydraulic pressure sensor monitoring the hydraulicactuator, etc. prior to the first FWT action. The FWT normal operationsequencer 252 may cause the first FWT action to be completed when thestatus of the component and/or the system of the FWT apparatus 154,156prior to the first FWT action is determined to be responsive. Forexample, the FWT normal operation sequencer 252 may cause a generationof a command to execute the first FWT action to be generated,transmitted, executed, etc. In some examples, the FWT normal operationsequencer 252 identifies and/or executes a second FWT action based on acompletion of the first FWT action. The completion of the first FWTaction may be determined by a measurement of a sensor. For example, thesecond FWT action may not be executed until the sensor measurementindicates that the first FWT action is complete. In some instances, theFWT normal operation sequencer 252 identifies and/or executes a secondFWT stage based on the completion of the first FWT action. Additionallyor alternatively, the FWT normal operation sequencer 252 may obtaininformation related to the components and/or the systems involved in thefirst FWT action during and/or after the first FWT action.

The sequence and control module 250 of FIGS. 2A and 2B includes the FWTnon-responsive sequencer 254 to determine a non-responsive sequence ofFWT stages and/or FWT actions. In some examples, the FWT non-responsesequencer 254 determines a non-responsive sequence based on anon-responsive status of a component and/or a system. For example, theFWT non-responsive sequencer 254 may determine a non-responsive sequencebased on the non-responsive status of a component and/or a system of theFWT apparatus 154,156. In some examples, the non-responsive statusindicates that an FWT stage and/or an FWT action may not be executed.For example, a non-responsive status of a hydraulic actuator operativelycoupled to a latch pin indicates that a retraction of the latch pin maynot be executed.

In some examples, the FWT non-responsive sequencer 254 identifies anon-responsive sequence of one or more FWT stages and/or FWT actionswhen a component status and/or a system status is a non-responsivestatus. In some instances, the FWT non-responsive sequencer 254determines a non-responsive sequence of the FWT stages and thecorresponding FWT actions to move the moveable surfaces 134,136 to anintermediate position. For example, the FWT non-responsive sequencer 254may determine the non-responsive sequence of FWT stages andcorresponding FWT actions to move the moveable surfaces 134,136 from theextended positions 142,144 to a position in between the extendedpositions 142,144 and the folded positions 146,148. In some examples,the FWT non-responsive sequencer 254 determines the non-responsivesequence of the FWT stages and/or the FWT actions for an FWT apparatusto remain in place. For example, the FWT non-responsive sequencer 254may determine a non-responsive sequence of the FWT stages and/or the FWTactions for the moveable surfaces 134,136 to remain in the foldedpositions 146,148. In another example, the FWT non-responsive sequencer254 may obtain a non-responsive status from a hydraulic actuatornecessary to move the moveable surfaces 134,136 from the foldedpositions 146,148 to the extended positions 142,144. In response toobtaining the non-responsive status from the hydraulic actuator, the FWTnon-responsive sequencer 254 may determine the FWT stages and/or the FWTactions necessary to maintain the moveable surfaces 134,136 in thefolded positions 146,148.

In some examples, the FWT non-responsive sequencer 254 calculates and/oridentifies a desired position of the FWT apparatus 154,156 based on theobtained information. The desired position may be, for example, theextended positions 142,144 of FIG. 1 or a position between the extendedpositions 142,144 and the folded positions 146,148 of FIG. 1. In someinstances, the FWT non-responsive sequencer 254 identifies the desiredposition to be the current position of the moveable surfaces 134,136.For example, the FWT non-responsive sequencer 254 may identify thedesired position of the moveable surfaces 134,136 of FIG. 1 to be thefolded positions 146,148. For example, the FWT non-responsive sequencer254 may calculate a desired position of the moveable surfaces 134,136 ofthe FWT apparatus 154,156 based on a non-responsive component status.The FWT normal operation sequencer 252 may generate one or more stagesand/or actions to cause the moveable surfaces 134,136 of the FWTapparatus 154,156 to move to the desired position from the currentposition of the moveable surfaces 134,136.

The sequence and control module 250 of FIGS. 2A and 2B includes thestatus evaluator 256 to evaluate a status of a component and/or a systemof an FWT apparatus. For example, the status evaluator 256 may evaluatea status of a component and/or a system of the FWT apparatus 154,156 ofFIG. 1. In some examples, the status evaluator 256 obtains a status of acomponent from the database 270. For example, the status evaluator 256may obtain a status of a pneumatic actuator of the FWT apparatus 154from the database 270. The status evaluator 256 may evaluate the statusof the pneumatic actuator and determine whether the status is normaloperation or non-responsive. In some instances, the status evaluator 256obtains a status of a system. For example, the status evaluator 256 mayobtain a status of a pneumatic system of the FWT apparatus 154. Thestatus evaluator 256 may evaluate the status of the pneumatic system anddetermine whether the status is normal operation or non-responsive.

The sequence and control module 250 of FIGS. 2A and 2B includes the FWTcontroller 258 to control a component and/or a system of an FWTapparatus. For example, the FWT controller 258 may control a componentand/or a system of the FWT apparatus 154,156 of FIG. 1. In someexamples, the FWT controller 258 generates a command. For example, theFWT controller 258 may generate a command for the FWT apparatus 154 tomove the moveable surface 134 of FIG. 1 from the folded position 146 tothe extended position 142. In some examples, the FWT controller 258generates the command to engage an interlock. For example, the FWTcontroller 258 may generate the command to engage a mechanical interlockand/or a software interlock. In some instances, the FWT controller 258generates the command to engage the interlock based on the status of thecomponent and/or the system. In some examples, the FWT controller 258transmits a command to a remote electronics unit. For example, the FWTcontroller 258 may transmit a command to the REUs 168,170 of FIG. 1.

In some examples, the FWT controller 258 executes a sequence of commandsin accordance with the FWT stages and/or the FWT actions generated bythe FWT normal operation sequencer 252 or the FWT non-responsivesequencer 254. In some examples, the FWT controller 258 executes thesequence of commands to complete one or more FWT actions based on astatus of a component and/or a system. For example, the FWT controller258 may issue a first command to a first component of the FWT apparatus154 to execute a first FWT action within a first FWT stage. The FWTcontroller 258 may receive the status of the first component indicatingthat the first command was executed and completed successfully. The FWTcontroller 258 may determine that the first FWT action is complete basedon the status of the first component. In response to determining thatthe first FWT action is complete, the FWT controller 258 may issue asecond command to a second component of the FWT apparatus 154,156 toexecute a second FWT action within the first FWT stage.

In some examples, the FWT controller 258 executes a sequence of commandsto complete one or more FWT stages based on a status of a componentand/or a system. For example, the FWT controller 258 may issue a firstcommand to a component of the FWT apparatus 154,156 to execute a firstFWT action within a first FWT stage. The FWT controller 258 may receivea status of the component indicating that the first command was executedand completed successfully. The FWT controller 258 may determine thatthe first FWT action is complete based on the component status. The FWTcontroller 258 may also determine that the first FWT stage is completebased on the completion of the first FWT action. In response todetermining that the first FWT stage is complete, the FWT controller 258may issue a second command to a component of the FWT apparatus 154,156to execute a first FWT action within a second FWT stage. In someexamples, the FWT controller 258 sets a flag (e.g., a completion flag)when the FWT stage and/or the FWT action is complete.

The gatekeeper module 280 of FIGS. 2A and 2B includes an example commandinterceptor 282, an example FWT apparatus analyzer 284, an exampleflight stage analyzer 286, an example maintenance enabler 288, anexample safety interlocker 290, and an example command transmitter 292.The gatekeeper module 280 includes the command interceptor 282 to obtainor intercept a command issued from the sequence and control module 250.In some examples, the command interceptor 282 obtains the command fromthe database 270. For example, the sequence and control module 250 mayissue the command and store the command in the database 270. The commandinterceptor 282 may obtain the stored command from the database 270.

The gatekeeper module 280 of FIGS. 2A and 2B includes the FWT apparatusanalyzer 284 to analyze an FWT apparatus and generate one or more rulesbased on a status of a component and/or a system of the FWT apparatus.For example, the FWT apparatus analyzer 284 may generate one or more FWTapparatus or status rules based on a status of the component and/or asystem of the FWT apparatus 154,156 of FIG. 1. A first example FWTapparatus rule may include not sending a command to a component and/or asystem that has a non-responsive status. Thus, sending a command to acomponent that has a non-responsive status violates the first exampleFWT apparatus rule. A second example FWT apparatus rule may include notsending a command to a component and/or a system that is not enabled.Thus, sending a command to a component and/or a system that is notenabled violates the second example FWT apparatus rule.

A third example FWT apparatus rule may include not sending a command toa component and/or a system that is incompatible with a status of thecomponent and/or the system. A fourth example FWT apparatus rule mayinclude not sending a command to a first component and/or a first systemthat is incompatible with a status of a second component and/or a secondsystem, where the first component and the first system are related tothe second component and the second system. For example, a primary lockof the FWT apparatus 154 is in the locked position and the moveablesurface 134 is in the extended position 142. The outgoing electroniccommand may be to adjust the moveable surface 134 to the folded position146. The FWT apparatus analyzer 284 may determine that adjusting themoveable surface 134 to the folded position 146 is incompatible with theprimary lock being in the locked position. Thus, the FWT apparatusanalyzer 284 may determine that the outgoing electronic command is aviolation of the fourth example FWT apparatus rule.

In some examples, the FWT apparatus analyzer 284 regenerates the FWTapparatus rules every process control cycle of the FWT control modules158,160. In some instances, the FWT apparatus rule may be retrieved fromthe database 270. For example, the FWT apparatus analyzer 284 mayretrieve the FWT apparatus rule from the database 270 at the beginningof the process control cycle. In some examples, the FWT apparatusanalyzer 284 may store the FWT apparatus rule in the database 270. Forexample, the FWT apparatus analyzer 284 may store the FWT apparatus rulein the database 270 at the end of the process control cycle.

The gatekeeper module 280 of FIGS. 2A and 2B includes the flight stageanalyzer 286 to analyze flight stage information of an aircraft andgenerate one or more rules based on the flight stage information. Forexample, the flight stage analyzer 286 may generate one or more flightstage rules based on the flight stage of the aircraft 100 of FIG. 1. Afirst example flight stage rule may include not actuating a componentand/or a system when the flight stage indicates that the aircraft is inflight. For example, moving the moveable surface 134 of FIG. 1 from theextended position 142 to the folded position 146 while the flight stageindicates that the aircraft is in flight is a violation of the firstexample flight stage rule. A second example flight stage rule mayinclude not actuating a component and/or a system when the flight stageindicates that the aircraft is docked at an airport gate. For example,moving the moveable surface 134 from the folded position 146 to theextended position 142 while the flight stage indicates that the aircraftis docked at the airport gate is a violation of the second exampleflight stage rule.

In some examples, the flight stage analyzer 286 regenerates the flightstage rules every process control cycle of the FWT control modules158,160. In some instances, the flight stage rule may be retrieved fromthe database 270. For example, the flight stage analyzer 286 mayretrieve the flight stage rule from the database 270 at the beginning ofthe process control cycle. In some examples, the flight stage analyzer286 may store the FWT apparatus rule in the database 270. For example,the flight stage analyzer 286 may store the flight stage rule in thedatabase 270 at the end of the process control cycle.

The gatekeeper module 280 of FIGS. 2A and 2B includes the maintenanceenabler 288 to enable a maintenance mode of an FWT control module. Forexample, the maintenance enabler 288 may enable the maintenance mode(s)of the FWT apparatus 154,156 of FIG. 1. In some examples, maintenancepersonnel operate the FWT apparatus 154,156 in a maintenance mode(s) ortest mode(s) to perform component checks and/or system checks. Forexample, the maintenance personnel may enable the maintenance mode byactuating a button, a knob, a switch, etc. accessible by the maintenancepersonnel. The button, the knob, the switch, etc. may set a flag and/oran alert within the maintenance enabler 288. The maintenance enabler 288may allow the maintenance personnel to operate individual componentsand/or individual systems of the FWT apparatus 154,156. For example, themaintenance enabler 288 may allow the maintenance personnel to outputcustom outgoing electronic commands to the components and/or the systemsof the FWT apparatus 154,156.

In the illustrated example of FIGS. 2A and 2B, the gatekeeper module 280includes the safety interlocker 290 to provide valid output electroniccommands to the FWT apparatus 154,156. In some examples, the safetyinterlocker 290 engages a safety interlock (e.g., a mechanicalinterlock, a software interlock, etc.) by modifying the outgoingelectronic command. In some instances, the safety interlock prevents anaction from occurring (e.g., canceling a command, dropping a command,etc.) or altering the action (e.g., modifying the command). In someinstances, the outgoing electronic command is obtained from the database270. For example, the sequence and control module 250 may generate acommand and store the command in the database 270. The safetyinterlocker 290 may obtain the command from the database 270 anddetermine if the command is valid.

In some examples, the safety interlocker 290 modifies the outgoingelectronic command based on a violation of the rules generated and/orevaluated by the FWT apparatus analyzer 284, the flight stage analyzer286, etc. For example, a hydraulic actuation system may not be enabledand the moveable surfaces 134,136 of FIG. 1 are in the extended position142. The outgoing electronic command may be to control the hydraulicactuation system to adjust the moveable surfaces 134,136 from theextended positions 142,144 to the folded positions 146,148. In responseto determining that the hydraulic actuation system is not enabled, theFWT apparatus analyzer 284 may determine that the outgoing electroniccommand violated an FWT apparatus rule. In response to the violation ofthe FWT apparatus rule, the safety interlocker 290 may modify theoutgoing electronic command to provide a valid command to the componentof the FWT apparatus 154,156. For example, the safety interlocker 290may modify the outputs 298 of the FWT control modules 158,160 to providethe valid command to the component of the FWT apparatus 154,156.

In some examples, the safety interlocker 290 may modify the outgoingelectronic command by replacing a value of the outgoing electroniccommand with a zero value or a null character. In some instances, thesafety interlocker 290 may modify the outgoing electronic command byreplacing the value of the outgoing electronic command with a storeddefault value. For example, the safety interlocker 290 may replace thevalue of the outgoing electronic command with the stored default valueobtained from the database 270 via the network 294. In some instances,the safety interlocker 290 may set a flag (e.g., a rules violation flag,an invalid input flag, an alert flag, etc.) alerting the FWT controlmodules 158,160 that the outgoing electronic command is invalid. Forexample, the safety interlocker 290 may set a rules violation flag whenthe outgoing electronic command violates one or more rules generated bythe FWT apparatus analyzer 284, the flight stage analyzer 286, etc.

In some examples, the gatekeeper module 280 of FIGS. 2A and 2B mayinclude the safety interlocker 290 to modify the outgoing electroniccommand to an aircraft control surface. For example, the safetyinterlocker 290 may modify the outgoing electronic command to theaircraft control surface by replacing a value of the outgoing electroniccommand with a zero value or a null character. In some instances, thesafety interlocker 290 may modify the outgoing electronic command byreplacing the value of the outgoing electronic command to the aircraftcontrol surface with a stored default value. For example, the safetyinterlocker 290 may replace the value of the outgoing electronic commandto the aircraft control surface with the stored default value obtainedfrom the database 270 via the network 294. In some instances, the safetyinterlocker 290 may set a flag (e.g., a rules violation flag, an invalidinput flag, an invalid output flag, an alert flag, etc.) alerting theFWT control modules 158,160 or an aircraft process control system thatthe outgoing electronic command is invalid.

The gatekeeper module 280 of FIGS. 2A and 2B includes the commandtransmitter 292 to output a command generated and/or processed from theFWT control modules 158,160. In some examples, the command transmitter292 outputs a modified command or a modified command. For example, thecommand transmitter 292 may transmit the modified command or theunmodified command as the output 298. In some examples, the commandtransmitter 292 transmits the command to a remote electronics unit(REU). For example, the command transmitter 292 may transmit the commandto the REUs 168,170 of FIG. 1. In some examples, the FWT control modules158,160 control a component and/or a system of an FWT apparatusconnected to the REUs 168,170 via the command transmitter 292. Forexample, the command transmitter 292 may relay or transmit the commandgenerated by the FWT controller 258 to the REUs 168,170.

While an example manner of implementing the example FWT control modules158,160 of FIG. 1 are illustrated in FIGS. 2A and 2B, one or more of theelements, processes and/or devices illustrated in FIGS. 2A and 2B may becombined, divided, re-arranged, omitted, eliminated and/or implementedin any other way. Further, the example collection module 200, theexample network interface 202, the example sensor interface 204, theexample information processor 206, the example information validator208, the example detection module 210, the example flight deck inputdetector 212, the example flight stage detector 214, the example FWTstatus detector 216, the example FWT detent detector 218, the exampleFWT lock detector 220, the example enable system module 230, the exampleFWT apparatus enabler 232, the example FWT apparatus actuator systemenabler 234, the example REU enabler 236, the example component enabler238, the example monitor and annunciation module 240, the examplenon-responsive status classifier 242, the example alert generator 244,the example alert manager 246, the example user interface informationprovider 248, the example sequence and control module 250, the exampleFWT normal operation sequencer 252, the example FWT non-responsivesequencer 254, the example status evaluator 256, the example FWTcontroller 258, the example database 270, the example gatekeeper module280, the example command interceptor 282, the example FWT apparatusanalyzer 284, the example flight stage analyzer 286, the examplemaintenance enabler 288, the example safety interlocker 290, the examplecommand transmitter 292, and/or, more generally, the example FWT controlmodules 158,160 of FIGS. 2A and 2B may be implemented by hardware,software, firmware and/or any combination of hardware, software and/orfirmware. Thus, for example, any of the example collection module 200,the example network interface 202, the example sensor interface 204, theexample information processor 206, the example information validator208, the example detection module 210, the example flight deck inputdetector 212, the example flight stage detector 214, the example FWTstatus detector 216, the example FWT detent detector 218, the exampleFWT lock detector 220, the example enable system module 230, the exampleFWT apparatus enabler 232, the example FWT apparatus actuator systemenabler 234, the example REU enabler 236, the example component enabler238, the example monitor and annunciation module 240, the examplenon-responsive status classifier 242, the example alert generator 244,the example alert manager 246, the example user interface informationprovider 248, the example sequence and control module 250, the exampleFWT normal operation sequencer 252, the example FWT non-responsivesequencer 254, the example status evaluator 256, the example FWTcontroller 258, the example database 270, the example gatekeeper module280, the example command interceptor 282, the example FWT apparatusanalyzer 284, the example flight stage analyzer 286, the examplemaintenance enabler 288, the example safety interlocker 290, the examplecommand transmitter 292, and/or, more generally, the example FWT controlmodules 158,160 of FIGS. 2A and 2B could be implemented by one or moreanalog or digital circuit(s), logic circuits, programmable processor(s),application specific integrated circuit(s) (ASIC(s)), programmable logicdevice(s) (PLD(s)) and/or field programmable logic device(s) (FPLD(s)).When reading any of the apparatus or system claims of this patent tocover a purely software and/or firmware implementation, at least one ofthe example collection module 200, the example network interface 202,the example sensor interface 204, the example information processor 206,the example information validator 208, the example detection module 210,the example flight deck input detector 212, the example flight stagedetector 214, the example FWT status detector 216, the example FWTdetent detector 218, the example FWT lock detector 220, the exampleenable system module 230, the example FWT apparatus enabler 232, theexample FWT apparatus actuator system enabler 234, the example REUenabler 236, the example component enabler 238, the example monitor andannunciation module 240, the example non-responsive status classifier242, the example alert generator 244, the example alert manager 246, theexample user interface information provider 248, the example sequenceand control module 250, the example FWT normal operation sequencer 252,the example FWT non-responsive sequencer 254, the example statusevaluator 256, the example FWT controller 258, the example database 270,the example gatekeeper module 280, the example command interceptor 282,the example FWT apparatus analyzer 284, the example flight stageanalyzer 286, the example maintenance enabler 288, the example safetyinterlocker 290, the example command transmitter 292, and/or, moregenerally, the example FWT control modules 158,160 of FIGS. 2A and 2Bis/are hereby expressly defined to include a tangible computer readablestorage device or storage disk such as a memory, a digital versatiledisk (DVD), a compact disk (CD), a Blu-ray disk, etc. storing thesoftware and/or firmware. Further still, the example FWT control modules158,160 of FIGS. 2A and 2B may include one or more elements, processesand/or devices in addition to, or instead of, those illustrated in FIGS.2A and 2B, and/or may include more than one of any or all of theillustrated elements, processes and devices.

Flowcharts representative of example methods for implementing theexample FWT control modules 158,160 of FIGS. 2A and 2B are shown inFIGS. 3-12. In these examples, the methods may be implemented usingmachine readable instructions that comprise a program for execution by aprocessor such as the processor 1312 shown in the example processorplatform 1300 discussed below in connection with FIG. 13. The programmay be embodied in software stored on a tangible computer readablestorage medium such as a CD-ROM, a floppy disk, a hard drive, a digitalversatile disk (DVD), a Blu-ray disk, or a memory associated with theprocessor 1312, but the entire program and/or parts thereof couldalternatively be executed by a device other than the processor 1312and/or embodied in firmware or dedicated hardware. Further, although theexample program is described with reference to the flowchartsillustrated in FIGS. 3-12, many other methods of implementing theexample FWT control modules 158,160 may alternatively be used. Forexample, the order of execution of the blocks may be changed, and/orsome of the blocks described may be changed, eliminated, or combined.

As mentioned above, the example methods of FIGS. 3-12 may be implementedusing coded instructions (e.g., computer and/or machine readableinstructions) stored on a tangible computer readable storage medium suchas a hard disk drive, a flash memory, a read-only memory (ROM), acompact disk (CD), a digital versatile disk (DVD), a cache, arandom-access memory (RAM) and/or any other storage device or storagedisk in which information is stored for any duration (e.g., for extendedtime periods, permanently, for brief instances, for temporarilybuffering, and/or for caching of the information). As used herein, theterm tangible computer readable storage medium is expressly defined toinclude any type of computer readable storage device and/or storage diskand to exclude propagating signals and to exclude transmission media. Asused herein, “tangible computer readable storage medium” and “tangiblemachine readable storage medium” are used interchangeably. Additionallyor alternatively, the example processes of FIGS. 3-12 may be implementedusing coded instructions (e.g., computer and/or machine readableinstructions) stored on a non-transitory computer and/or machinereadable medium such as a hard disk drive, a flash memory, a read-onlymemory, a compact disk, a digital versatile disk, a cache, arandom-access memory and/or any other storage device or storage disk inwhich information is stored for any duration (e.g., for extended timeperiods, permanently, for brief instances, for temporarily buffering,and/or for caching of the information). As used herein, the termnon-transitory computer readable medium is expressly defined to includeany type of computer readable storage device and/or storage disk and toexclude propagating signals and to exclude transmission media. As usedherein, when the phrase “at least” is used as the transition term in apreamble of a claim, it is open-ended in the same manner as the term“comprising” is open ended. Comprising and all other variants of“comprise” are expressly defined to be open-ended terms. Including andall other variants of “include” are also defined to be open-ended terms.In contrast, the term consisting and/or other forms of consist aredefined to be close-ended terms.

FIG. 3 is a flowchart representative of an example method 300 that maybe performed by the example FWT control modules 158,160 of FIGS. 2A and2B to determine and execute an FWT sequence of events to control the FWTapparatus 154,156 of FIG. 1. For example, the FWT control modules158,160 may determine whether to execute a normal operation FWT sequenceof events or a non-responsive FWT sequence of events. The example method300 begins at block 302 when the FWT control modules 158,160 obtain andprocess inputs from an aircraft process control system. For example, thecollection module 200 may obtain and process the inputs 296. At block304, the FWT control modules 158,160 determine status informationcorresponding to the FWT apparatus, and, more generally, the aircraftprocess control system. For example, the detection module 210 may detectand/or determine status information of the FWT apparatus 154,156 and theaircraft 100.

At block 306, the FWT control modules 158,160 determine whether toenable the FWT system. For example, the enable system module 230 maydetermine whether determined status information indicates enabling theFWT apparatus 154,156. If, at block 306, the FWT control modules 158,160determine not to enable the FWT system, then control returns to block302 to obtain and process additional inputs. For example, the statusinformation of the FWT apparatus 154,156 may not indicate that the FWTsystem is to be enabled. If, at block 306, the FWT control modules158,160 determine to enable the FWT system, then, at block 308, the FWTcontrol modules 158,160 enable the FWT system. For example, the statusinformation of the FWT apparatus 154,156 may indicate that the FWTsystem is to be enabled.

At block 308, the FWT control modules 158,160 enable the FWT system. Forexample, the enable system module 230 enables the FWT system. At block310, the FWT control modules 158,160 evaluate the status information.For example, the sequence and control module 250 may evaluate the statusinformation. At block 312, the FWT control modules 158,160 determinewhether the status information includes a non-responsive status. Forexample, the sequence and control module 250 may determine whether thestatus information includes a non-responsive status. If, at block 312,the FWT control modules 158,160 determine that the status informationdoes not include a non-responsive status, then, at block 318, the FWTcontrol modules 158,160 execute an FWT normal operation sequence for theFWT apparatus 154,156. If, at block 312, the FWT control modules 158,160determine that the status information includes a non-responsive status,then, at block 314, the FWT control modules 158,160 process thenon-responsive status.

At block 314, the FWT control modules 158,160 process the non-responsivestatus. For example, the monitor and annunciation module 240 may processthe non-responsive status. At block 316, the FWT control modules 158,160determine whether the non-responsive status can be mitigated. Forexample, the monitor and annunciation module 240 may determine whetherthe non-responsive status can be mitigated. If, at block 316, the FWTcontrol modules 158,160 determine that the non-responsive status can bemitigated, then, at block 318, the FWT control modules 158,160 execute anormal operation sequence. If, at block 316, the FWT control modules158,160 determine that the non-responsive status cannot be mitigated,control proceeds to block 322 to execute an FWT non-responsive sequence.

At block 318, the FWT control modules 158,160 execute the FWT normaloperation sequence. For example, the sequence and control module 250 maygenerate and execute an FWT normal operation sequence, where the FWTnormal operation sequence may include one or more FWT stages and/or FWTactions. At block 320, the FWT control modules 158,160 determine whetherthe FWT normal operation sequence completed. For example, the sequenceand control module 250 may determine whether the FWT normal operationsequence completed. If, at block 320, the FWT control modules 158,160determine that the FWT normal operation sequence did not complete, then,at block 322, the FWT control modules 158,160 execute the FWTnon-responsive sequence. For example, the sequence and control module250 may generate and execute an FWT non-responsive sequence, where theFWT non-responsive sequence may include one or more FWT stages and/orFWT actions. If, at block 320, the FWT control modules 158,160 determinethat the FWT normal operation sequence completed, then the examplemethod 300 concludes.

Additional detail in connection with obtaining and processing inputs(FIG. 3 block 302) is shown in FIG. 4. FIG. 4 is a flowchartrepresentative of an example method 400 that may be performed by the FWTcontrol modules 158,160 of FIGS. 2A and 2B to obtain and process inputs.The example method 400 begins at block 402 when the collection module200 obtains inputs. For example, the collection module 200 may obtainthe inputs 296 via the network interface 202 or the sensor interface204. At block 404, the collection module 200 selects an input toprocess. For example, the information processor 206 may select an input296 to process. At block 406, the collection module 200 processes theinput. For example, the information processor 206 may process the input296 by converting (e.g., converting using a conversion calculation,converting to different units of measure, etc.), scaling (e.g., scalingusing a scaling factor), and/or translating (e.g., translating using apre-determined curve, translating using a pre-determined equation) thevalue of the input 296.

At block 408, the collection module 200 validates the input. Forexample, the information validator 208 may validate the input 296. Atblock 410, the collection module 200 determines whether the input isvalid. For example, the information validator 208 may determine whetherthe input 296 is valid. If, at block 410, the collection module 200determines that the input is valid, then, at block 414, the collectionmodule 200 stores the processed input in a database. For example, theinformation validator 208 may store the input 296 in the database 270 inresponse to determining that the input 296 is valid. If, at block 410,the collection module 200 determines that the input is invalid, controlproceeds to block 412 to process the invalid input. At block 412, thecollection module 200 processes the invalid input. For example, theinformation validator 208 may determine that the input 296 has a valuethat is out of the range of acceptable values for the input 296 and, inresponse, determines that the input 296 is invalid. At block 414, thecollection module 200 stores the processed input in a database. Forexample, the information validator 208 may store the input 296 in thedatabase 270. At block 416, the collection module 200 determines whetherthere is another input to process. If, at block 416, the collectionmodule 200 determines there is another input to process, control returnsto block 404 to select another input to process, otherwise the examplemethod 400 concludes.

Additional detail in connection with determining status information(FIG. 3 block 304) is shown in FIG. 5. FIG. 5 is a flowchartrepresentative of an example method 500 that may be performed by the FWTcontrol modules 158,160 of FIGS. 2A and 2B to determine statusinformation of an FWT apparatus, and, more generally an aircraft processcontrol system. The example method 500 begins at block 502 when the FWTcontrol modules 158,160 detect and determine flight deck input statusinformation. For example, the flight deck input detector 212 maydetermine a status of a flight deck input from a cockpit or a flightdeck of an aircraft. At block 504, the FWT control modules 158,160determine flight stage status information. For example, the flight stagedetector 214 may determine a status of a flight stage of the aircraft.At block 506, the FWT control modules 158,160 determine folding wingtip(FWT) status information. For example, the FWT status detector maydetermine a status or statuses of the FWT apparatus 154,156 of FIG. 1.At block 508, the FWT control modules 158,160 determine FWT detentstatus information. For example, the FWT detent detector 218 maydetermine a status of a latch or an additional locking mechanism of theFWT apparatus 154,156. At block 510, the FWT control modules 158,160determine FWT lock status information. For example, the FWT lockdetector 220 may determine a status of a primary lock, a secondary lock,etc. of the FWT apparatus 154,156.

Additional detail in connection with enabling the FWT system (FIG. 3block 308) is shown in FIG. 6. FIG. 6 is a flowchart representative ofan example method 600 that may be performed by the FWT control modules158,160 of FIGS. 2A and 2B to enable the FWT system. The example method600 begins at block 602 when the FWT control modules 158,160 enable anFWT apparatus. For example, the FWT apparatus enabler 232 may set a flag(e.g., an enable FWT apparatus flag) for the FWT apparatus 154,156alerting the FWT control modules 158,160 that the FWT apparatus 154,156are enabled. At block 604, the FWT control modules 158,160 enable one ormore FWT apparatus actuator systems. For example, the FWT apparatusactuator system enabler 234 may set a flag (e.g., an enable FWTapparatus actuator system flag) for an FWT apparatus actuator system ofthe FWT apparatus 154,156, alerting the FWT control modules 158,160 thatthe FWT apparatus actuator system is enabled.

At block 606, the FWT control modules 158,160 enable one or more remoteelectronics units (REUs). For example, the REU enabler 236 may set aflag (e.g., an enable REU flag) for the REUs 168,170 of FIG. 1, alertingthe FWT control modules 158,160 that the REUs 168,170 are enabled. Atblock 608, the FWT control modules 158,160 enable one or morecomponents. For example, the component enabler 238 may set a flag (e.g.,an enable component flag) for one or more components of the FWTapparatus 154,156 alerting the FWT control modules 158,160 that the oneor more components are enabled.

Additional detail in connection with processing non-responsive statuses(FIG. 3 block 314) is shown in FIG. 7. FIG. 7 is a flowchartrepresentative of an example method 700 that may be performed by the FWTcontrol modules 158,160 of FIGS. 2A and 2B to process a non-responsivestatus. The example method 700 begins at block 702 when the FWT controlmodules 158,160 obtain non-responsive status information. For example,the non-responsive status classifier 242 may obtain the non-responsivestatus information from the database 270. At block 704, the FWT controlmodules 158,160 select a non-responsive status to process. For example,the non-responsive status classifier 242 may select the non-responsivestatus to process.

At block 706, the FWT control modules 158,160 determine whether thenon-responsive status is due to a component. For example, thenon-responsive status classifier 242 may determine whether thenon-responsive status is due to a component status. If, at block 706,the FWT control modules 158,160 determine that the non-responsive statusis not due to the component, control proceeds to block 714 to generatean alert. If, at block 706, the FWT control modules 158,160 determinethat the non-responsive status is due to the component, then, at block708, the FWT control modules 158,160 determine whether there is aredundant component. For example, the non-responsive status classifier242 may determine whether the component has one or more backup orredundant components in response to the component having anon-responsive status. If, at block 708, the FWT control modules 158,160determine that there is not a redundant component, control proceeds toblock 714 to generate an alert. If, at block 708, the FWT controlmodules 158,160 determine that there is a redundant component, then, atblock 710, the FWT control modules 158,160 replace an input from thenon-responsive component with an input from the redundant component. Forexample, the non-responsive status classifier 242 may set a flag (e.g.,a redundant component flag), alerting the FWT control modules 158,160 todisable the non-responsive component data channel and enable theredundant component data channel. For example, the collection module 200may disable the non-responsive component data channel and enable theredundant component data channel.

At block 712, the FWT control modules 158,160 set a mitigation flag. Forexample, the non-responsive status classifier 242 may set the mitigationflag, alerting the FWT control modules 158,160 that the component withthe non-responsive status may be mitigated. At block 714, the FWTcontrol modules 158,160 generate an alert. For example, the alertgenerator 244 may generate an alert such as, for example, displaying analert on a user interface, propagating an alert message throughout aprocess control network, generating an alert log and/or a report, etc.At block 716, the FWT control modules 158,160 manage the alert. Forexample, the alert manager 246 may process the generated alert by addingthe alert in an alert list, an alert log, an alert report, etc. At block718, the FWT control modules 158,160 transmit the alert information(e.g., the alert list, the alert log, the alert report, etc.) to a userinterface. For example, the user interface information provider 248 mayassign information related to generated alerts to variables associatedwith an FWT apparatus user interface. At block 720, the FWT controlmodules 158,160 determine whether there is another non-responsive statusto process. If, at block 720, the FWT control modules 158,160 determinethere is another non-responsive status to process, control returns toblock 704 to select another non-responsive status to process, otherwisethe example method 700 concludes.

Additional detail in connection with executing an FWT normal operationsequence (FIG. 3 block 318) is shown in FIG. 8. FIG. 8 is a flowchartrepresentative of an example method 800 that may be performed by the FWTcontrol modules 158,160 of FIGS. 2A and 2B to execute the FWT normaloperation sequence. The example method 800 begins at block 802 when theFWT control modules 158,160 determine whether the FWT status is flightmode. For example, the status evaluator 256 may evaluate the FWT statusand determine if the FWT status is the flight mode, the folded mode,etc. If, at block 802, the FWT control modules 158,160 determine thatthe FWT status is the flight mode, then, at block 804, the FWT controlmodules 158,160 execute a folding operation sequence. For example, theFWT normal operation sequencer 252 may generate and execute an FWTnormal operation sequence to automatically move the folding wingtipsfrom the extended position to the folded position. The FWT normaloperation sequence may include one or more FWT stages and/or FWTactions. If, at block 802, the FWT control modules 158,160 determinethat the FWT status is not the flight mode (e.g., in folded mode) then,at block 806, the FWT control modules 158,160 execute an unfoldingoperation sequence. For example, the FWT normal operation sequencer 252may generate and execute an FWT normal operation sequence toautomatically move the folding wingtips from the folded position to theextended position.

Additional detail in connection with executing an example foldingoperation sequence (FIG. 8 block 804) is shown in FIG. 9. FIG. 9 is aflowchart representative of an example method 900 that may be performedby the FWT control modules 158,160 of FIGS. 2A and 2B to execute theexample folding operation sequence of the FWT apparatus 154,156 ofFIG. 1. The example method 900 begins at block 902 when the FWT controlmodules 158,160 obtain an FWT normal operation sequence. For example,the FWT normal operation sequencer 252 may determine the FWT normaloperation sequence. The FWT normal operation sequencer 252 may store theFWT normal operation sequence in the database 270. The FWT controller258 may obtain the FWT normal operation sequence from the FWT normaloperation sequencer 252 or from the database 270. At block 904 the FWTcontrol modules 158,160 open an isolation valve (e.g., a hydraulicvalve, a pneumatic valve, etc.). For example, the FWT controller 258 mayissue a command to the REU 168 of FIG. 1 via the command transmitter 292to open the isolation valve of the FWT apparatus 154. At block 906, theFWT control modules 158,160 determine whether the operation issuccessful. For example, the FWT controller 258 may determine whetherthe operation is successful based on a status change of the isolationvalve. For example, the FWT controller 258 may determine the isolationvalve status change based on a measurement of a sensor monitoring theisolation valve (e.g., a position sensor, a proximity sensor, etc.). If,at block 906, the FWT control modules 158,160 determine that theoperation is successful, then, at block 908, the FWT control modules158,160 move a secondary lock to a middle position, otherwise theexample method 900 concludes.

At block 908, the FWT control modules 158,160 move the secondary lock tothe middle position or an intermediate position. For example, the FWTcontroller 258 may issue a command to the REU 168 via the commandtransmitter 292 to move the secondary lock of the FWT apparatus 154 tothe middle position. At block 910, the FWT control modules 158,160determine whether the operation is successful. For example, the FWTcontroller 258 may determine whether the operation is successful basedon a status change of the secondary lock. If, at block 910, the FWTcontrol modules 158,160 determine that the operation is successful,then, at block 912, the FWT control modules 158,160 unlock a primarylock, otherwise the example method 900 concludes.

At block 912, the FWT control modules 158,160 unlock the primary lock.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to unlock the primary lock of the FWTapparatus 154. At block 914, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the primary lock. If, at block 914, the FWT control modules158,160 determine that the operation is successful, then, at block 916,the FWT control modules 158,160 retract latch pins, otherwise theexample method 900 concludes.

At block 916, the FWT control modules 158,160 retract the latch pins.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to retract the latch pins of the FWTapparatus 154. At block 918, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the latch pins. If, at block 918, the FWT control modules158,160 determine that the operation is successful, then, at block 920,the FWT control modules 158,160 move the secondary lock to an unlockedposition, otherwise the example method 900 concludes.

At block 920, the FWT control modules 158,160 move the secondary lock tothe unlocked position. For example, the FWT controller 258 may issue acommand to the REU 168 via the command transmitter 292 to move thesecondary lock of the FWT apparatus 154 to the unlocked position. Atblock 922, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on the status changeof the secondary lock. If, at block 922, the FWT control modules 158,160determine that the operation is successful, then, at block 924, the FWTcontrol modules 158,160 fold the wingtips, otherwise the example method900 concludes.

At block 924, the FWT control modules 158,160 fold the wingtips. Forexample, the FWT controller 258 may issue a command to the REU 168 viathe command transmitter 292 to move the moveable surface 134 of the FWTapparatus 154 from the extended position 142 to the folded position 146.At block 926, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on a status changeof the folding wingtips. If, at block 926, the FWT control modules158,160 determine that the operation is successful, then, at block 928the FWT control modules 158,160 engage a fold brake, otherwise theexample method 900 concludes.

At block 928, the FWT control modules 158,160 engage the fold brake. Forexample, the FWT controller 258 may issue a command to the REU 168 viathe command transmitter 292 to engage the fold brake of the FWTapparatus 154. At block 930, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the fold brake. If, at block 930, the FWT control modules158,160 determine that the operation is successful, then, at block 932the FWT control modules 158,160 move the secondary lock to the middleposition, otherwise the example method 900 concludes.

At block 932, the FWT control modules 158,160 move the secondary lock tothe middle position or the intermediate position. For example, the FWTcontroller 258 may issue a command to the REU 168 via the commandtransmitter 292 to move the secondary lock of the FWT apparatus 154 fromthe unlocked position to the middle position. At block 934, the FWTcontrol modules 158,160 determine whether the operation is successful.For example, the FWT controller 258 may determine whether the operationis successful based on the status change of the secondary lock. If, atblock 934, the FWT control modules 158,160 determine that the operationis successful, then, at block 936 the FWT control modules 158,160 extendthe latch pins, otherwise the example method 900 concludes.

At block 936, the FWT control modules 158,160 extend the latch pins. Forexample, the FWT controller 258 may issue a command to the REU 168 viathe command transmitter 292 to extend the latch pins of the FWTapparatus 154. At block 938, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on the statuschange of the latch pins. If, at block 938, the FWT control modules158,160 determine that the operation is successful, then, at block 940the FWT control modules 158,160 lock the primary lock, otherwise theexample method 900 concludes.

At block 940, the FWT control modules 158,160 lock the primary lock. Forexample, the FWT controller 258 may issue a command to the REU 168 viathe command transmitter 292 to move the primary lock of the FWTapparatus 154 from the unlocked position to the locked position. Atblock 942, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on the status changeof the primary lock. If, at block 942, the FWT control modules 158,160determine that the operation is successful, then, at block 944 the FWTcontrol modules 158,160 move the secondary lock to the locked position,otherwise the example method 900 concludes.

At block 944, the FWT control modules 158,160 move the secondary lock tothe locked position. For example, the FWT controller 258 may issue acommand to the REU 168 via the command transmitter 292 to move thesecondary lock of the FWT apparatus 154 from the middle position to thelocked position. At block 946, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on the statuschange of the secondary lock. If, at block 946, the FWT control modules158,160 determine that the operation is successful, then, at block 948the FWT control modules 158,160 close the isolation valve, otherwise theexample method 900 concludes.

At block 948, the FWT control modules 158,160 close the isolation valve.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to close the isolation valve of the FWTapparatus 154. At block 950, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on the statuschange of the isolation valve. If, at block 950, the FWT control modules158,160 determine that the operation is successful, then, at block 952the FWT control modules 158,160 set a completion flag, otherwise theexample method 900 concludes.

Additional detail in connection with opening an isolation valve (FIG. 9block 904) is shown in FIG. 10. FIG. 10 is a flowchart representative ofan example method 1000 that may be performed by the FWT control modules158,160 of FIGS. 2A and 2B to actuate a component of the FWT apparatus154,156 of FIG. 1. The example method 1000 may also be applied to theactions described in FIG. 9 blocks 904, 908, 912, 916, 920, 924, 928,932, 936, 940, 944, and 948. The example method 1000 begins at block1002 when the FWT control modules 158,160 obtain the component status.For example, the status evaluator 256 may obtain the isolation valvestatus from the database 270. At block 1004, the FWT control modules158,160 determine whether the component status is non-responsive. Forexample, the status evaluator 256 may determine whether the isolationvalve status is non-responsive. If, at block 1004, the FWT controlmodules 158,160 determine that the component is responsive, then, atblock 1006, the FWT control modules 158,160 generate a command. Forexample, the FWT controller 258 may generate a command.

At block 1008, the FWT control modules 158,160 validate the command. Forexample, the gatekeeper module 280 may validate the command. At block1010, the FWT control modules 158,160 sends the command. For example,the command transmitter 292 may send the command to the REU 168 ofFIG. 1. At block 1012, the FWT control modules 158,160 determine whetherthe component status changes. For example, the status evaluator 256 maydetermine whether the isolation valve opens based on a status change ofthe isolation valve. If, at block 1012, the FWT control modules 158,160determine that the component status changes, then, at block 1012, theFWT control modules 158,160 set a completion flag, otherwise the examplemethod 1000 concludes.

For example, the FWT controller 258 may set the completion flag.

If, at block 1004, the FWT control modules 158,160 determine that thecomponent status is non-responsive, then, at block 1014, the FWT controlmodules 158,160 process the component non-responsive status. Forexample, the FWT control modules 158,160 may process the componentnon-responsive status in accordance with the example method 700 asdescribed in FIG. 7. At block 1016, the FWT control modules 158,160determine whether the component non-responsive status can be mitigated.For example, the non-responsive status classifier 242 may determinewhether the isolation valve non-responsive status can be mitigated basedon whether a flag has been set (e.g., a mitigation flag has been set).If, at block 1016, the FWT control modules 158,160 determine that thecomponent non-responsive status can be mitigated, control returns toblock 1002 to obtain the component status (e.g., obtain an updatedcomponent status), otherwise the example method 1000 concludes.

Additional detail in connection with validating the command (FIG. 10block 1008) is shown in FIG. 11. FIG. 11 is a flowchart representativeof an example method 1100 that may be performed by the FWT controlmodules 158,160 of FIGS. 2A and 2B to validate an outgoing electroniccommand from the FWT controller 258, and, more generally, the FWTcontrol modules 158,160. The example method 1100 begins at block 1102when the FWT control modules 158,160 obtain the command. For example,the command interceptor 282 may obtain the command by intercepting thecommand from the FWT controller 258.

At block 1104, the FWT control modules 158,160 determine whether thecommand violates an FWT apparatus rule. For example, the FWT apparatusanalyzer 284 may determine whether the command violates one or more FWTapparatus rules. If, at block 1104, the FWT control modules 158,160determine that the command violates the one or more FWT apparatus rules,then, at block 1106, the FWT control modules 158,160 modify the commandwith a stored command. For example, the safety interlocker 290 mayreplace the command (e.g., the value of the command) with the storedcommand obtained from the database 270. If, at block 1104, the FWTcontrol modules 158,160 determine that the command does not violate theone or more FWT apparatus rules, then, at block 1108, the FWT controlmodules 158,160 determine whether the command violates a flight stagerule. For example, the flight stage analyzer 286 may determine whetherthe command violates one or more flight stage rules. If, at block 1108,the FWT control modules 158,160 determine that the command violates theone or more flight stage rules, then, at block 1110, the FWT controlmodules 158,160 cancel the command. For example, the safety interlocker290 may cancel the command by discarding or dropping the command. Inanother example, the safety interlocker 290 may replace the command witha zero value, a null index, a null character, etc. If, at block 1108,the FWT control modules 158,160 determine that the command does notviolate the one or more flight stage rules, then the example method 1100concludes.

Additional detail in connection with executing an example unfoldingoperation sequence (FIG. 8 block 806) is shown in FIG. 12. FIG. 12 is aflowchart representative of an example method 1200 that may be performedby the FWT control modules 158,160 of FIGS. 2A and 2B to execute theexample unfolding operation sequence of the FWT apparatus 154,156 ofFIG. 1. The example method 1200 begins at block 1202 when the FWTcontrol modules 158,160 obtain an FWT normal operation sequence. Forexample, the FWT normal operation sequencer 252 may determine the FWTnormal operation sequence. The FWT normal operation sequencer 252 maystore the FWT normal operation sequence in the database 270. The FWTcontroller 258 may obtain the FWT normal operation sequence from the FWTnormal operation sequencer 252 or from the database 270. At block 1204the FWT control modules 158,160 open an isolation valve (e.g., ahydraulic valve, a pneumatic valve, etc.). For example, the FWTcontroller 258 may issue a command to the REU 168 of FIG. 1 via thecommand transmitter 292 to open the isolation valve of the FWT apparatus154. At block 1206, the FWT control modules 158,160 determine whetherthe operation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on a status changeof the isolation valve. If, at block 1206, the FWT control modules158,160 determine that the operation is successful, then, at block 1208,the FWT control modules 158,160 move a secondary lock to a middleposition, otherwise the example method 1200 concludes.

At block 1208, the FWT control modules 158,160 move the secondary lockto the middle position or an intermediate position. For example, the FWTcontroller 258 may issue a command to the REU 168 via the commandtransmitter 292 to move the secondary lock of the FWT apparatus 154 tothe middle position. At block 1210, the FWT control modules 158,160determine whether the operation is successful. For example, the FWTcontroller 258 may determine whether the operation is successful basedon a status change of the secondary lock. If, at block 1210, the FWTcontrol modules 158,160 determine that the operation is successful,then, at block 1212, the FWT control modules 158,160 unlock a primarylock, otherwise the example method 1200 concludes.

At block 1212, the FWT control modules 158,160 unlock the primary lock.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to unlock the primary lock of the FWTapparatus 154. At block 1214, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the primary lock. If, at block 1214, the FWT control modules158,160 determine that the operation is successful, then, at block 1216,the FWT control modules 158,160 retract latch pins, otherwise theexample method 1200 concludes.

At block 1216, the FWT control modules 158,160 retract the latch pins.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to retract the latch pins of the FWTapparatus 154. At block 1218, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the latch pins. If, at block 1218, the FWT control modules158,160 determine that the operation is successful, then, at block 1220,the FWT control modules 158,160 move the secondary lock to an unlockedposition, otherwise the example method 1200 concludes.

At block 1220, the FWT control modules 158,160 move the secondary lockto the unlocked position. For example, the FWT controller 258 may issuea command to the REU 168 via the command transmitter 292 to move thesecondary lock of the FWT apparatus 154 to the unlocked position. Atblock 1222, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on the status changeof the secondary lock. If, at block 1222, the FWT control modules158,160 determine that the operation is successful, then, at block 1224,the FWT control modules 158,160 engage a fold brake, otherwise theexample method 1200 concludes.

At block 1224, the FWT control modules 158,160 engage the fold brake.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to engage the fold brake of the FWTapparatus 154. At block 1226, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on a statuschange of the fold brake. If, at block 1226, the FWT control modules158,160 determine that the operation is successful, then, at block 1228the FWT control modules 158,160 unfold the wingtips, otherwise theexample method 1200 concludes.

At block 1228, the FWT control modules 158,160 unfold the wingtips. Forexample, the FWT controller 258 may issue a command to the REU 168 viathe command transmitter 292 to move the moveable surface 134 of the FWTapparatus 154 from the folded position 146 to the extended position 142.At block 1230, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on a status changeof the folding wingtips. If, at block 1230, the FWT control modules158,160 determine that the operation is successful, then, at block 1232the FWT control modules 158,160 move the secondary lock to the middleposition, otherwise the example method 1200 concludes.

At block 1232, the FWT control modules 158,160 move the secondary lockto the middle position or the intermediate position. For example, theFWT controller 258 may issue a command to the REU 168 via the commandtransmitter 292 to move the secondary lock of the FWT apparatus 154 fromthe unlocked position to the middle position. At block 1234, the FWTcontrol modules 158,160 determine whether the operation is successful.For example, the FWT controller 258 may determine whether the operationis successful based on the status change of the secondary lock. If, atblock 1234, the FWT control modules 158,160 determine that the operationis successful, then, at block 1236 the FWT control modules 158,160extend the latch pins, otherwise the example method 1200 concludes.

At block 1236, the FWT control modules 158,160 extend the latch pins.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to extend the latch pins of the FWTapparatus 154. At block 1238, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on the statuschange of the latch pins. If, at block 1238, the FWT control modules158,160 determine that the operation is successful, then, at block 1240the FWT control modules 158,160 lock the primary lock, otherwise theexample method 1200 concludes.

At block 1240, the FWT control modules 158,160 lock the primary lock.For example, the FWT controller 258 may issue a command to the REU 168via the command transmitter 292 to move the primary lock of the FWTapparatus 154 from the unlocked position to the locked position. Atblock 1242, the FWT control modules 158,160 determine whether theoperation is successful. For example, the FWT controller 258 maydetermine whether the operation is successful based on the status changeof the primary lock. If, at block 1242, the FWT control modules 158,160determine that the operation is successful, then, at block 1244 the FWTcontrol modules 158,160 move the secondary lock to the locked position,otherwise the example method 1200 concludes.

At block 1244, the FWT control modules move the secondary lock to thelocked position. For example, the FWT controller 258 may issue a commandto the REU 168 via the command transmitter 292 to move the secondarylock of the FWT apparatus 154 from the middle position to the lockedposition. At block 1246, the FWT control modules 158,160 determinewhether the operation is successful. For example, the FWT controller 258may determine whether the operation is successful based on the statuschange of the secondary lock. If, at block 1246, the FWT control modules158,160 determine that the operation is successful, then, at block 1248the FWT control modules 158,160 close the isolation valve, otherwise theexample method 1200 concludes.

At block 1248, the FWT control modules 158,160 close the isolationvalve. For example, the FWT controller 258 may issue a command to theREU 168 via the command transmitter 292 to close the isolation valve ofthe FWT apparatus 154. At block 1250, the FWT control modules 158,160determine whether the operation is successful. For example, the FWTcontroller 258 may determine whether the operation is successful basedon the status change of the isolation valve. If, at block 1250, the FWTcontrol modules 158,160 determine that the operation is successful,then, at block 1252 the FWT control modules 158,160 set a completionflag, otherwise the example method 1200 concludes.

The above-described methods of FIGS. 3-12 may be applicable to the FWTcontrol module 158, the FWT control module 160, and/or a combinationthereof. In some examples, the above-described methods of FIGS. 3-12 areapplicable to one or more FWT control modules. For example, theabove-described methods of FIGS. 3-12 may be applicable to the FWTcontrol module 158, the FWT control module 160, a third FWT controlmodule, etc. and/or a combination thereof.

FIG. 13 is a block diagram of an example processor platform 1300 capableof executing instructions to implement the methods of FIGS. 3-12 and theapparatus of FIGS. 2A and 2B. The processor platform 1300 can be, forexample, a server, an industrial computer, or any other type ofcomputing device.

The processor platform 1300 of the illustrated example includes aprocessor 1312. The processor 1312 of the illustrated example ishardware. For example, the processor 1312 can be implemented by one ormore integrated circuits, logic circuits, microprocessors or controllersfrom any desired family or manufacturer.

The processor 1312 of the illustrated example includes a local memory1313 (e.g., a cache). The processor 1312 of the illustrated exampleexecutes the instructions to implement the example FWT control modules158,160. The processor 1312 of the illustrated example is incommunication with a main memory including a volatile memory 1314 and anon-volatile memory 1316 via a bus 1318. The volatile memory 1314 may beimplemented by Synchronous Dynamic Random Access Memory (SDRAM), DynamicRandom Access Memory (DRAM), RAMBUS Dynamic Random Access Memory (RDRAM)and/or any other type of random access memory device. The non-volatilememory 1316 may be implemented by flash memory and/or any other desiredtype of memory device. Access to the main memory 1314,1316 is controlledby a memory controller.

The processor platform 1300 of the illustrated example also includes aninterface circuit 1320. The interface circuit 1320 may be implemented byany type of interface standard, such as an Ethernet interface, auniversal serial bus (USB), and/or a PCI express interface.

In the illustrated example, one or more input devices 1322 are connectedto the interface circuit 1320. The input device(s) 1322 permit(s) a userto enter data and commands into the processor 1312. The input device(s)can be implemented by, for example, a keyboard, a button, a mouse, atouchscreen, a track-pad, a trackball, isopoint and/or a voicerecognition system.

One or more output devices 1324 are also connected to the interfacecircuit 1320 of the illustrated example. The output devices 1324 can beimplemented, for example, by display devices (e.g., a light emittingdiode (LED), an organic light emitting diode (OLED), a liquid crystaldisplay, a cathode ray tube display (CRT), a touchscreen, a tactileoutput device, a printer and/or speakers). The interface circuit 1320 ofthe illustrated example, thus, typically includes a graphics drivercard, a graphics driver chip or a graphics driver processor.

The interface circuit 1320 of the illustrated example also includes acommunication device such as a transmitter, a receiver, a transceiver, amodem and/or network interface card to facilitate exchange of data withexternal machines (e.g., computing devices of any kind) via a network1326 (e.g., an Ethernet connection, a digital subscriber line (DSL), atelephone line, coaxial cable, a cellular telephone system, etc.).

The processor platform 1300 of the illustrated example also includes oneor more mass storage devices 1328 for storing software and/or data.Examples of such mass storage devices 1328 include floppy disk drives,hard drive disks, compact disk drives, Blu-ray disk drives, RAIDsystems, and digital versatile disk (DVD) drives. The example massstorage 1328 implements the example database 270.

Coded instructions 1332 to implement the methods of FIGS. 3-12 may bestored in the mass storage device 1328, in the volatile memory 1314, inthe non-volatile memory 1316, and/or on a removable tangible computerreadable storage medium such as a CD or DVD.

From the foregoing, it will be appreciated that the above disclosedfolding wingtip control module and methods obtain status informationcorresponding to the above disclosed folding wingtip apparatus and, moregenerally, an aircraft process control system. As a result, the abovedisclosed folding wingtip control module and methods generate a sequenceof stages and events to be executed in succession to automatically foldand extend the above disclosed folding wingtip apparatus based on theobtained status information. The sequence of stages and events areexecuted based on a command validated by the above disclosed foldingwingtip control module.

Although certain example methods, apparatus and articles of manufacturehave been disclosed herein, the scope of coverage of this patent is notlimited thereto. On the contrary, this patent covers all methods,apparatus and articles of manufacture fairly falling within the scope ofthe claims of this patent.

What is claimed is:
 1. An apparatus comprising: a detection module to:determine a status of a component of a folding wingtip assemblyoperatively coupled to a wing of an aircraft; and determine a flightstage of the aircraft; a sequence and control module to generate acommand to control a movement of the folding wingtip assembly; and agatekeeper module to validate the command based on the status and theflight stage.
 2. The apparatus of claim 1, wherein the status is anoperational status of the component.
 3. The apparatus of claim 1,wherein the flight stage includes whether the aircraft is in flight orin motion on a ground surface.
 4. The apparatus of claim 1, wherein thegatekeeper module includes: a folding wingtip apparatus analyzer togenerate a status rule based on the status; and a flight stage analyzerto generate a flight stage rule based on the flight stage.
 5. Theapparatus of claim 4, wherein the gatekeeper module is to modify thecommand when the command violates the status rule or the flight stagerule.
 6. The apparatus of claim 5, wherein the gatekeeper module is tomodify the command by replacing the command with a previously determinedcommand.
 7. A method comprising: determining a status of a component ofa folding wingtip assembly operatively coupled to a wing of an aircraft;determining a flight stage of the aircraft; generating a command tocontrol a movement of the folding wingtip assembly; and validating, byexecuting an instruction with a processor, the command based on thestatus and the flight stage.
 8. The method of claim 7, wherein thestatus is an operational status of the component.
 9. The method of claim7, wherein the flight stage includes whether the aircraft is in flightor in motion on a ground surface.
 10. The method of claim 7, whereinvalidating the command includes generating a status rule based on thestatus and generating a flight stage rule based on the flight stage. 11.The method of claim 10, further including dropping the command when thecommand violates the status rule or the flight stage rule.
 12. Themethod of claim 10, further including modifying the command when thecommand violates the status rule or the flight stage rule.
 13. Themethod of claim 12, wherein modifying the command includes replacing thecommand with a previously determined command.
 14. A tangiblecomputer-readable storage medium comprising instructions that, whenexecuted, cause a machine to at least: determine a status of a componentof a folding wingtip assembly operatively coupled to a wing of anaircraft; determine a flight stage of the aircraft; generate a commandto control a movement of the folding wingtip assembly; and validate thecommand based on the status and the flight stage.
 15. The tangiblecomputer-readable storage medium of claim 14, wherein the status is anoperational status of the component.
 16. The tangible computer-readablestorage medium of claim 14, wherein flight stage includes whether theaircraft is in flight or in motion on a ground surface.
 17. The tangiblecomputer-readable storage medium of claim 14, wherein validating thecommand includes generating a status rule based on the status andgenerating a flight stage rule based on the flight stage.
 18. Thetangible computer-readable storage medium of claim 17, further includinginstructions that when executed, cause the machine to drop the commandwhen the command violates the status rule or the flight stage rule. 19.The tangible computer-readable storage medium of claim 17, furtherincluding instructions that when executed, cause the machine to modifythe command when the command violates the status rule or the flightstage rule.
 20. The tangible computer-readable storage medium of claim19, wherein modifying the command includes replacing the command with apreviously determined command.